Papers › Autoregressive flow-based causal discovery and inference

Autoregressive flow-based causal discovery and inference

18 Jul 2020arXiv:2007.09390archive 2025-07-28

Ricardo Pio Monti, Ilyes Khemakhem, Aapo Hyvarinen

We posit that autoregressive flow models are well-suited to performing a range of causal inference tasks - ranging from causal discovery to making interventional and counterfactual predictions. In particular, we exploit the fact that autoregressive architectures define an ordering over variables, analogous to a causal ordering, in order to propose a single flow architecture to perform all three aforementioned tasks. We first leverage the fact that flow models estimate normalized log-densities of data to derive a bivariate measure of causal direction based on likelihood ratios. Whilst traditional measures of causal direction often require restrictive assumptions on the nature of causal relationships (e.g., linearity),the flexibility of flow models allows for arbitrary causal dependencies. Our approach compares favourably against alternative methods on synthetic data as well as on the Cause-Effect Pairs bench-mark dataset. Subsequently, we demonstrate that the invertible nature of flows naturally allows for direct evaluation of both interventional and counterfactual predictions, which require marginalization and conditioning over latent variables respectively. We present examples over synthetic data where autoregressive flows, when trained under the correct causal ordering, are able to make accurate interventional and counterfactual predictions

PaperPDFCodeCode Syntology ranMethod as code

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

The archive's official repository (piomonti/AffineFlowCausalInf) was not harvested; the 15 samples below come from 1 community repository.

Syntology 15 code samples harvested from 1 repository linked to this paper: 11 ran (of which 10 constructed an object rather than computing a result; 10 with no instrument failure: 0 honoured, 0 violated, 10 with no contract checked; 1 where Syntology's instrument failed) · 4 unverified. Where Syntology's instrument failed: 1 where our contract draft was wrong; failures of Syntology's instrument, not of the code.

By repository: community (archive-listed): 15 samples from 1 repository, 11 ran (10 with no instrument failure; 1 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 on 2026-09-22 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

piomonti/AffineFlowCausalInf officialmentioned in papermentioned on GitHubpytorchSyntology: not harvested report
piomonti/carefl mentioned on GitHubpytorchSyntology: 15 samples, 11 ran (1 instrument-failed) · 4 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

15 samples harvested: 11 ran (of which 10 constructed an object rather than computing a result; 10 with no instrument failure: 0 honoured, 0 violated, 10 with no contract checked; 1 where Syntology's instrument failed) · 4 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.

1ran · our draft was wrong
10ran
4unverified

Licence: 0 of the 15 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 piomonti/carefl. “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”. For 9 samples that ran, the graph records a signature this page does not show: for a class the fixture built without calling, the harness called the object with inputs it made up itself, so the recorded signature is the harness's probe, not the fixture's arguments. “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.

piomonti/carefl community (archive-listed) 15 samples, 11 ran (1 instrument-failed) · 4 unverified
ARMLP models/carefl.py ran · metamorphic tier: deterministic fingerprinted MIT (permissive) · b793bc8bea09122a · report fixture: returned ARMLP · level recorded 2026-09-22
AffineCL models/carefl.py ran · metamorphic tier: deterministic MIT (permissive) · ee35a766a467c7ab · report fixture: returned AffineCL · level recorded 2026-09-22
CustomSyntheticDatasetDensity models/carefl.py ran MIT (permissive) · da6d3d9a336b2a9c · report fixture: returned CustomSyntheticDatasetDensity · level recorded 2026-09-22
MADE in 7 papers models/carefl.py ran · metamorphic tier: deterministic fingerprinted MIT (permissive) · 03e61cb03e4a473b · report fixture: returned MADE · level recorded 2026-09-22
MAF models/carefl.py ran · metamorphic tier: deterministic MIT (permissive) · 49de88957949ca25 · report fixture: returned MAF · level recorded 2026-09-22
MLP1layer models/carefl.py ran · metamorphic tier: deterministic fingerprinted MIT (permissive) · 756d26a591b1b7cf · report fixture: returned MLP1layer · level recorded 2026-09-22
MLP4 models/carefl.py ran · metamorphic tier: deterministic fingerprinted MIT (permissive) · 2eefac96b1b3db97 · report fixture: returned MLP4 · level recorded 2026-09-22
MaskedLinear in 9 papers models/carefl.py ran · metamorphic tier: deterministic MIT (permissive) · ed7abf1170b542ee · report fixture: returned MaskedLinear · level recorded 2026-09-22
NormalizingFlow models/carefl.py ran · metamorphic tier: deterministic fingerprinted MIT (permissive) · 003866981408459c · report fixture: returned NormalizingFlow · level recorded 2026-09-22
NormalizingFlowModel models/carefl.py ran · metamorphic tier: deterministic fingerprinted MIT (permissive) · 332907cc3fc9bc91 · report fixture: returned NormalizingFlowModel · level recorded 2026-09-22
unconstrained_RQS models/carefl.py ran · our draft was wrong MIT (permissive) · af7c19b8eaf6e4a4 · report fixture: signature inputs:Tensor/1/float, unnormalized_widths:Tensor/2/float, unnormalized_heights:Tensor/2/float, unnormalized_derivatives:Tensor/2/float, inverse:bool/0/bool, tail_bound:float/0/float, min_bin_width:float/0/float, min_bin_height:float/0/float, min_derivative:float/0/float · returned tuple · level recorded 2026-09-22
CAREFL models/carefl.py unverified MIT (permissive) · c201e2ca52b456ff · report
NSF_AR models/carefl.py unverified MIT (permissive) · 87c69bdae0f2ca05 · report
RQS models/carefl.py unverified MIT (permissive) · db027a8f670e12d3 · report
searchsorted in 9 papers models/carefl.py unverified MIT (permissive) · e85d747983c4f5d8 · report

Method as code Syntology

What Syntology's graph records as this paper's claimed method, lifted into code: each assembly names its bricks (functions and classes), each with its own role and its own verification level. An assembly is not a check that the code implements the method correctly or reproduces the paper's results. Levels are each brick's own verification level in Syntology's graph (level 0: no recorded run), listed brick by brick and never combined into one level; “ran” means the brick executed on a synthesized input, not that its output is correct, and the instrument figure counts failures of Syntology's instrument, not of the code. Where a model read the code against the paper's claim, each assembly's label verdict is one model's judgement, kept in this page's JSON twin; it is not calibrated, so no card prints it. Siblings are assemblies lifted from this paper in the same batch for the same method: alternative readings kept side by side; none replaces or supersedes another.

2 assemblies on this paper: 2 harvested, 0 generated, listed in 1 groups (siblings lifted in one batch form one group).

2 sibling assemblies for autoregressive flow-based causal discovery and inference (harvested), lifted in the same batch on 2026-09-09: alternative readings kept side by side; none replaces or supersedes another.

harvested Assembly for autoregressive flow-based causal discovery and inference (graph method: autoregressive flow-based causal discovery and inference). 15 bricks; individually on a fixture: 11 ran (of which 10 constructed an object rather than computing a result; 10 with no instrument failure: 0 honoured, 0 violated, 10 with no contract checked; 1 where Syntology's instrument failed) · 4 unverified. The assembly has not been run end-to-end.

one of 2 siblings

  1. CAREFL entry · level 0 · unverified · c201e2ca52b456ff
  2. ARMLP model · level 1 · ran · b793bc8bea09122a
  3. AffineCL model · level 1 · ran · ee35a766a467c7ab
  4. CustomSyntheticDatasetDensity helper · level 1 · ran · da6d3d9a336b2a9c
  5. MAF model · level 1 · ran · 49de88957949ca25
  6. MLP1layer helper · level 1 · ran · 756d26a591b1b7cf
  7. MLP4 helper · level 1 · ran · 2eefac96b1b3db97
  8. NSF_AR helper · level 0 · unverified · 87c69bdae0f2ca05
  9. NormalizingFlowModel model · level 1 · ran · 332907cc3fc9bc91
  10. MADE model · level 1 · ran · 03e61cb03e4a473b
  11. unconstrained_RQS helper · level 1 · ran · our draft was wrong · af7c19b8eaf6e4a4
  12. NormalizingFlow model · level 1 · ran · 003866981408459c
  13. MaskedLinear helper · level 1 · ran · ed7abf1170b542ee
  14. RQS helper · level 0 · unverified · db027a8f670e12d3
  15. searchsorted helper · level 0 · unverified · e85d747983c4f5d8

harvested Assembly for autoregressive flow-based causal discovery and inference (graph method: autoregressive flow-based causal discovery and inference). 4 bricks; individually on a fixture: 4 ran (of which 4 constructed an object rather than computing a result; 4 with no instrument failure: 0 honoured, 0 violated, 4 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified; every one of the 4 samples that ran constructed an object rather than computing a result. The assembly has not been run end-to-end.

one of 2 siblings

  1. MAF entry · level 1 · ran · 49de88957949ca25
  2. ARMLP model · level 1 · ran · b793bc8bea09122a
  3. MADE model · level 1 · ran · 03e61cb03e4a473b
  4. MaskedLinear helper · level 1 · ran · ed7abf1170b542ee

Each brick ends with its code_sha256, Syntology's identity for that exact code; click one to copy the get_code call that returns it. For agents, on Syntology's MCP service: assembly(arxiv_id="2007.09390") returns these assemblies with each brick's role and wiring (how to connect).

Tasks

Causal DiscoveryCausal Inference

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.

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