Papers › Estimating individual treatment effect: generalization bounds and algorithms

Estimating individual treatment effect: generalization bounds and algorithms

13 Jun 2016ICML 2017 8arXiv:1606.03976archive 2025-07-28

Uri Shalit, Fredrik D. Johansson, David Sontag

There is intense interest in applying machine learning to problems of causal inference in fields such as healthcare, economics and education. In particular, individual-level causal inference has important applications such as precision medicine. We give a new theoretical analysis and family of algorithms for predicting individual treatment effect (ITE) from observational data, under the assumption known as strong ignorability. The algorithms learn a "balanced" representation such that the induced treated and control distributions look similar. We give a novel, simple and intuitive generalization-error bound showing that the expected ITE estimation error of a representation is bounded by a sum of the standard generalization-error of that representation and the distance between the treated and control distributions induced by the representation. We use Integral Probability Metrics to measure distances between distributions, deriving explicit bounds for the Wasserstein and Maximum Mean Discrepancy (MMD) distances. Experiments on real and simulated data show the new algorithms match or outperform the state-of-the-art.

PaperPDFConference PDFCodeCode Syntology ran

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, on Syntology's MCP service (how to connect):

Code

Syntology 5 code samples harvested from 1 repository linked to this paper: 5 ran (of which 0 constructed an object rather than computing a result; 5 with no instrument failure: 0 honoured, 0 violated, 5 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code; here there are none.

By repository: community (archive-listed): 5 samples from 1 repository, 5 ran (5 with no instrument failure; 0 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

No sample is linked to this paper from 1 of its repositories that Syntology harvested for other papers:

Levels written on 2026-09-26 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

clinicalml/cfrnet mentioned on GitHubtfMITSyntology: not harvested report
oddrose/cfrnet mentioned on GitHubtfSyntology: not harvested report
sschrod/bites mentioned on GitHubpytorchBSD-2-ClauseSyntology: 5 samples, 5 ran (0 instrument-failed) · 0 unverified report
xinshuli2022/cite mentioned on GitHubtfMITSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Adversarial Balancing-based Representation Learning for Causal Effect Inference with... (arXiv:1904.13335; that paper's own run record: 18 ran (of which 0 constructed an object rather than computing a result; 17 with no instrument failure: 0 honoured, 0 violated, 17 with no contract checked; 1 where Syntology's instrument failed) · 5 unverified); nothing checks that they implement this paper's method. report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

A paper named beside a repository with no sample linked to this paper is shown with that paper's own run record, not this paper's: “ran” means executed on a synthesized input, not that the code is correct, and “where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Papers are listed in arXiv-id order, at most three per repository.

Code Syntology ran Syntology

5 samples harvested: 5 ran (of which 0 constructed an object rather than computing a result; 5 with no instrument failure: 0 honoured, 0 violated, 5 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page has not changed since , the first build that kept a record date for it; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

5ran

Licence: 0 of the 5 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from sschrod/bites. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

sschrod/bites community (archive-listed) 5 samples, 5 ran (0 instrument-failed) · 0 unverified
concordance_td bites/utils/concordance.py ran BSD-2-Clause (permissive) · 8129e8abb094c8f1 · report fixture: signature durations:ndarray/1/float, events:ndarray/1/int, surv:ndarray/2/float, surv_idx:ndarray/1/int, method:str/0/str · returned float · level recorded 2026-09-26
cox_ph_loss bites/utils/loss.py ran BSD-2-Clause (permissive) · 82838449bf144f9e · report fixture: signature log_h:Tensor/1/float, durations:Tensor/1/float, events:Tensor/1/float, eps:float/0/float · returned Tensor · level recorded 2026-09-26
cox_ph_loss_sorted bites/utils/loss.py ran fingerprinted BSD-2-Clause (permissive) · 8a1945abc2aa367a · report fixture: signature log_h:Tensor/1/float, events:Tensor/1/float, eps:float/0/float · returned Tensor · level recorded 2026-09-26
idx_at_times bites/utils/utils.py ran BSD-2-Clause (permissive) · da646f8263b84ea4 · report fixture: signature index_surv:ndarray/1/float, times:ndarray/1/float, steps:str/0/str, assert_sorted:bool/0/bool · returned ndarray · level recorded 2026-09-26
kaplan_meier bites/utils/utils.py ran BSD-2-Clause (permissive) · 6e33868d39c90a75 · report fixture: signature durations:ndarray/1/float, events:ndarray/1/int, start_duration:int/0/int · returned Series · level recorded 2026-09-26

Tasks

Causal InferenceGeneralization BoundsHeterogeneous Treatment Effect Estimation

Datasets

Introduced by this paper, per the archive.

IHDPJobs

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Causal Inference IHDP Counterfactual Regression + WASS Average Treatment Effect Error 0.27 #5 of 13 Archive leaderboard report
Causal Inference IHDP TARNet Average Treatment Effect Error 0.28 #6 of 13 Archive leaderboard report
Causal Inference IHDP Causal Forest Average Treatment Effect Error 0.4 #8 of 13 Archive leaderboard report
Causal Inference IHDP Balancing Neural Network Average Treatment Effect Error 0.42 #9 of 13 Archive leaderboard report
Causal Inference IHDP k-NN Average Treatment Effect Error 0.79 #11 of 13 Archive leaderboard report
Causal Inference IHDP Balancing Linear Regression Average Treatment Effect Error 0.93 #12 of 13 Archive leaderboard report
Causal Inference IHDP Random Forest Average Treatment Effect Error 0.96 #13 of 13 Archive leaderboard report
Causal Inference Jobs CFR MMD Average Treatment Effect on the Treated Error 0.08 #3 of 5 Archive leaderboard report
Causal Inference Jobs CFR WASS Average Treatment Effect on the Treated Error 0.09 #5 of 5 Archive leaderboard report
Heterogeneous Treatment Effect Estimation IHDP TARNet PEHE 0.95 #2 of 2 Archive leaderboard report

Ranks are positions in the archive's leaderboards as they stood at the 2025-07-28 snapshot. Results published since then are not among these rows, so a rank here is not a current standing.

Methods

Causal inference

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections