graphdml
Causal effects on networks, with honest confidence intervals.
When a treatment reaches one person, it often reaches their friends too: a vaccine protects the neighbors, a coupon gets shared, a training spreads by word of mouth. graphdml estimates both effects separately:
- the direct effect: what the treatment does for the person who receives it
- the peer effect: what it does for the people connected to them
It uses double machine learning with any scikit-learn model, adjusts for confounding that runs through the network, and reports confidence intervals that account for neighbors being dependent. Graphs can come from pandas, networkx or Neo4j, and results can be written back to Neo4j.
Install
pip install "git+https://github.com/Samrdreyfuss/graphdml.git" # core
pip install "graphdml[neo4j] @ git+https://github.com/Samrdreyfuss/graphdml.git"
Requires Python 3.10+. Core dependencies: numpy, scipy, pandas, scikit-learn.
Quickstart
from graphdml import GraphDML
from graphdml.datasets import make_flu_town
ds = make_flu_town() # 5,000 residents; true effects: -2.0 and -0.5 sick days
model = GraphDML(exposure="sum", random_state=0).fit(ds.data)
print(model.summary())
coef std err z P>|z| [2.5% 97.5%]
direct -1.879 0.1275 -14.73 0.000 -2.129 -1.629
peer:sum -0.4341 0.0689 -6.30 0.000 -0.5692 -0.2991
direct: change in Y when own treatment goes 0 → 1
peer:sum: change in Y per additional treated neighbor
The full summary also reports diagnostics, warnings and the assumptions the estimate relies on. Methods that ignore the network get this example wrong, because health-conscious residents cluster together:
from graphdml.baselines import compare_methods
compare_methods(ds.data, exposure="sum", truth=ds.truth)
| Method | Effect | Estimate | 95% CI | Truth |
|---|---|---|---|---|
| OLS, no network | direct | −2.39 | [−2.52, −2.26] | −2.0 ✗ |
| OLS + exposure, no neighbor covariates | peer | −0.66 | [−0.68, −0.63] | −0.5 ✗ |
| DML, own covariates only | direct | −2.41 | [−2.54, −2.28] | −2.0 ✗ |
| GraphDML | direct | −1.88 | [−2.13, −1.63] | −2.0 ✓ |
| GraphDML | peer | −0.43 | [−0.57, −0.30] | −0.5 ✓ |
Your own data
from graphdml import GraphData, GraphDML
from sklearn.ensemble import RandomForestClassifier, RandomForestRegressor
data = GraphData.from_pandas(
nodes, edges, # edges: source influences target
features=["age", "income"], treatment="treated", outcome="spend", node_id="user_id",
)
model = GraphDML(
model_y=RandomForestRegressor(min_samples_leaf=20), # any scikit-learn model
model_t=RandomForestClassifier(min_samples_leaf=20),
exposure="mean", # share of treated neighbors
).fit(data)
model.summary_frame() # estimates as a DataFrame
GraphData.from_edges and GraphData.from_networkx work too.
Neo4j
from graphdml.io.neo4j import Neo4jGraphSource, Neo4jResultWriter
src = Neo4jGraphSource(uri="bolt://localhost:7687", auth=("neo4j", "..."))
data = src.load("Customer", "FRIENDS_WITH", features=["age", "tenure"],
treatment="got_coupon", outcome="spend", id_property="customer_id")
model = GraphDML(exposure="mean").fit(data)
Neo4jResultWriter(driver=src.driver).write(
model, run_name="coupon-q3", node_label="Customer", id_property="customer_id")
Each run is stored as a (:GDMLRun) node linked to the nodes it was estimated on, with
per-node predictions and residuals, and never modifies your data. Try it locally with
docker compose up -d && python -m graphdml.demo --password graphdml-demo. The
Neo4j guide covers directed graphs, custom Cypher and GDS embeddings.
Example datasets
| Dataset | Story | Shows |
|---|---|---|
make_flu_town |
flu shots and sick days among neighbors | direct vs peer effects, network confounding |
make_referral_app |
promo coupons in an app with influencers | choosing the exposure map |
make_classroom_tutoring |
tutoring hours and test scores | continuous treatment, who the estimate is about |
make_homophily_trap |
a course whose true peer effect is zero | a failure mode and how to catch it |
make_lastfm_promo |
a promotion on the real LastFM Asia network | real topology and covariates, known truth |
load_insurance_experiment |
a randomized field experiment with 4,902 farmers | real data (download from openICPSR) |
Every dataset comes with a story card: print(ds.DESCR).
Checking an analysis
from graphdml import negative_control_test, placebo_test, two_hop_test
placebo_test(model, data) # shuffled treatment: no effect?
negative_control_test(model, data, last_year_y) # an outcome T can't affect: no effect?
two_hop_test(model, data) # do friends-of-friends matter?
No estimator can rule out unobserved confounding on its own; these checks flag common ways an analysis goes wrong.
How it works
- Features. Each node's covariates are combined with aggregates of its neighbors' covariates, so the models can learn confounding that runs through the network.
- Focal set. Estimates use nodes whose neighborhoods do not overlap, so their contributions are independent. This set is the effective sample size.
- Cross-fitting. Nuisance models are trained on all data that is independent of the held-out nodes, then used to residualize treatment, peer exposure and outcome.
- Final stage. A robust moment condition gives the direct and peer effects, with sandwich (optionally cluster-robust) standard errors.
Details: methodology · design choices and evidence.
Validation
graphdml is tested against pre-specified criteria (protocol, results):
- Matches DoubleML and statsmodels exactly in the cases where they apply.
- 95% intervals cover at the nominal rate on simulated graphs with known truth.
- On the real LastFM Asia network (100 replications): bias under 2.5%, coverage 0.92–0.96. Network-blind methods were off by 37–71% and never covered.
- On the randomized insurance experiment, the direct effect matches the published estimate (0.148 vs 0.141).
Status
Alpha. Planned next: graph neural network nuisance models, dependence-robust inference that uses every node, and sensitivity analysis for unobserved confounding.
Acknowledgements and citation
The estimator builds on Khatami, Parikh, Chen, Roy and Salimi, Graph Machine Learning based Doubly Robust Estimator for Network Causal Effects (AISTATS 2025). Please cite their paper along with graphdml (CITATION.cff).
MIT licensed.
Metadata
Release files for graphdml 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| graphdml-0.1.0.tar.gz | 82.8 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| graphdml-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 148.7 kB
Release files / graphdml-0.1.0.tar.gz
| Download URL | graphdml-0.1.0.tar.gz |
|---|---|
| Size | 82.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ace8cb99720affb9eebcd33337b2de8548d4590fea4e34238a6fa2ef768d9432
|
|
BLAKE2b-256 checksum How to use checksums |
4b24889da475a5678ba23564f9d9133b8c51c7fd6e0fbac801ae92391c13623e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 6, 2026.
Transparency logRelease files / graphdml-0.1.0-py3-none-any.whl
| Download URL | graphdml-0.1.0-py3-none-any.whl |
|---|---|
| Size | 65.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d46e3e5cf32da1f7930e5c258cb407b419dc617dcba3baca451df3214a9a3bc5
|
|
BLAKE2b-256 checksum How to use checksums |
d1524143618b43a468bf86afea791eedcedd945dfde519b241d5f2f2658374fa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 6, 2026.
Transparency log