Papers › Continuous-Time Modeling of Counterfactual Outcomes Using Neural Controlled...

Continuous-Time Modeling of Counterfactual Outcomes Using Neural Controlled Differential Equations

16 Jun 2022arXiv:2206.08311archive 2025-07-28

Nabeel Seedat, Fergus Imrie, Alexis Bellot, Zhaozhi Qian, Mihaela van der Schaar

Estimating counterfactual outcomes over time has the potential to unlock personalized healthcare by assisting decision-makers to answer ''what-iF'' questions. Existing causal inference approaches typically consider regular, discrete-time intervals between observations and treatment decisions and hence are unable to naturally model irregularly sampled data, which is the common setting in practice. To handle arbitrary observation patterns, we interpret the data as samples from an underlying continuous-time process and propose to model its latent trajectory explicitly using the mathematics of controlled differential equations. This leads to a new approach, the Treatment Effect Neural Controlled Differential Equation (TE-CDE), that allows the potential outcomes to be evaluated at any time point. In addition, adversarial training is used to adjust for time-dependent confounding which is critical in longitudinal settings and is an added challenge not encountered in conventional time-series. To assess solutions to this problem, we propose a controllable simulation environment based on a model of tumor growth for a range of scenarios with irregular sampling reflective of a variety of clinical scenarios. TE-CDE consistently outperforms existing approaches in all simulated scenarios with irregular sampling.

PaperPDFCodeCode 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 12 code samples harvested from 2 repositories 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) · 7 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code; here there are none.

By repository: official repository: 12 samples from 2 repositories, 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.

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

seedatnabeel/te-cde officialmentioned in paperpytorchMITSyntology: 9 samples, 5 ran (0 instrument-failed) · 4 unverified report
vanderschaarlab/mlforhealthlabpub officialmentioned in papertfSyntology: 3 samples, 0 ran · 3 unverified 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.

Code Syntology ran Syntology

12 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) · 7 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
7unverified

Licence: 3 of the 12 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 2 repositories linked to this paper, official or community; the list below is grouped by repository, each group headed by its name and what it is to the paper. “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.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity.

seedatnabeel/te-cde official repository 9 samples, 5 ran (0 instrument-failed) · 4 unverified
calc_diameter src/utils/cancer_simulation.py ran MIT (permissive) · 49da0ce0fcbb45b8 · report fixture: signature volume:ndarray/0/float · returned float64 · level recorded 2026-09-26
calc_volume src/utils/cancer_simulation.py ran fingerprinted MIT (permissive) · b3ddbda44f74ad61 · report fixture: signature diameter:float/0/float · returned float · level recorded 2026-09-26
compute_cross_entropy_loss src/utils/losses.py ran MIT (permissive) · c333545f546b687b · report fixture: signature outputs:Tensor/2/float, predictions:Tensor/2/float, active_entries:Tensor/1/bool · returned Tensor · level recorded 2026-09-26
compute_norm_mse_loss src/utils/losses.py ran MIT (permissive) · 2ea6c82d486b437a · report fixture: signature ground_truth_outputs:Tensor/2/float, predictions:Tensor/2/float, active_entries:Tensor/2/float, norm:int/0/int · returned Tensor · level recorded 2026-09-25
enable_dropout src/utils/training_tools.py ran MIT (permissive) · 0001acc4d96a96b7 · report fixture: signature model:callable/0/? · returned ModelWithDropout · level recorded 2026-09-26
get_confounding_params src/utils/cancer_simulation.py unverified MIT (permissive) · 15186e50c588f77d · report
get_processed_data src/utils/data_utils.py unverified MIT (permissive) · d0c7de0d9a8420a0 · report
get_treatment_indices src/utils/data_utils.py unverified MIT (permissive) · 0aba1992b3caa924 · report
process_data in 61 papers src/utils/data_utils.py unverified MIT (permissive) · 2d8be4f367d27978 · report
vanderschaarlab/mlforhealthlabpub official repository 3 samples, 0 ran · 3 unverified
calc_diameter alg/counterfactual_recurrent_network/utils/cancer_simulation.py unverified licence not identified · pointer only · 0c0b2a070d31dc0e · report
calc_volume alg/counterfactual_recurrent_network/utils/cancer_simulation.py unverified licence not identified · pointer only · 741692c86b6c2e82 · report
get_confounding_params alg/counterfactual_recurrent_network/utils/cancer_simulation.py unverified licence not identified · pointer only · a8d4d124df84ab97 · report

Tasks

Causal InferenceTime SeriesTime Series Analysis

1 archive task tag without a task page not shown.

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

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