Papers › CaRiNG: Learning Temporal Causal Representation under Non-Invertible Generation Process

CaRiNG: Learning Temporal Causal Representation under Non-Invertible Generation Process

25 Jan 2024arXiv:2401.14535archive 2025-07-28

Guangyi Chen, Yifan Shen, Zhenhao Chen, Xiangchen Song, Yuewen Sun, Weiran Yao, Xiao Liu, Kun Zhang

Identifying the underlying time-delayed latent causal processes in sequential data is vital for grasping temporal dynamics and making downstream reasoning. While some recent methods can robustly identify these latent causal variables, they rely on strict assumptions about the invertible generation process from latent variables to observed data. However, these assumptions are often hard to satisfy in real-world applications containing information loss. For instance, the visual perception process translates a 3D space into 2D images, or the phenomenon of persistence of vision incorporates historical data into current perceptions. To address this challenge, we establish an identifiability theory that allows for the recovery of independent latent components even when they come from a nonlinear and non-invertible mix. Using this theory as a foundation, we propose a principled approach, CaRiNG, to learn the CAusal RepresentatIon of Non-invertible Generative temporal data with identifiability guarantees. Specifically, we utilize temporal context to recover lost latent information and apply the conditions in our theory to guide the training process. Through experiments conducted on synthetic datasets, we validate that our CaRiNG method reliably identifies the causal process, even when the generation process is non-invertible. Moreover, we demonstrate that our approach considerably improves temporal understanding and reasoning in practical applications.

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

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

By repository: official repository: 10 samples from 1 repository, 8 ran (8 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-22 and 2026-09-24 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

sanshuiii/caring officialmentioned in papermentioned on GitHubpytorchMITSyntology: 10 samples, 8 ran (0 instrument-failed) · 2 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

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

Licence: 0 of the 10 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 sanshuiii/caring. “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 3 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. A census tag appears when Syntology's census ran implementations with that name on one shared input per bucket: it gives how many were compared, from how many papers, and how many distinct outputs they produced, and names this sample's bucket when this sample was one of them.

sanshuiii/caring official repository 10 samples, 8 ran (0 instrument-failed) · 2 unverified
BetaVAE_MLP caring/modules/stationary.py ran fingerprinted MIT (permissive) · d4fd240849acc2b3 · report fixture: returned BetaVAE_MLP · level recorded 2026-09-22
Inference caring/modules/stationary.py ran MIT (permissive) · 773460f058b3b35c · report fixture: returned Inference · level recorded 2026-09-22
MLPDecoder caring/modules/stationary.py ran fingerprinted MIT (permissive) · d6c09b008d2e8fe3 · report fixture: returned MLPDecoder · level recorded 2026-09-22
MLPEncoder in 8 papers caring/modules/stationary.py ran fingerprinted MIT (permissive) · bfc5af9d3691e10d · report fixture: returned MLPEncoder · level recorded 2026-09-22
NPTransitionPrior caring/modules/stationary.py ran MIT (permissive) · bdecb548777436c9 · report fixture: returned NPTransitionPrior · level recorded 2026-09-22
concat_x_byx caring/datasets/checker.py ran MIT (permissive) · af54234bb8d55554 · report fixture: signature x:ndarray/3/float, y:ndarray/3/float, lag:int/0/int · returned tuple · level recorded 2026-09-24
concat_x_byy caring/datasets/checker.py ran MIT (permissive) · 819cc462002cb6c0 · report fixture: signature x:ndarray/3/float, y:ndarray/3/float, lag:int/0/int · returned tuple · level recorded 2026-09-24
reparametrize in 22 papers
census: 6 implementations from 8 papers, 1 distinct output on one shared input this sample: bucket 1 of 1, arg 1: rank 2, kind float, dtype float32 · arg 2: rank 2, kind float, dtype float32
caring/modules/components/beta.py ran · honoured contract fingerprinted MIT (permissive) · 863fc64cd51264f0 · report fixture: signature mu:Tensor/2/float, logvar:Tensor/2/float · returned Tensor · level recorded 2026-09-22
StationaryProcess caring/modules/stationary.py unverified MIT (permissive) · bec6363e2390b390 · report
check_lag_byx caring/datasets/checker.py unverified MIT (permissive) · efb4053bab2aa8c2 · 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.

1 assembly on this paper: 1 harvested, 0 generated.

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

  1. StationaryProcess entry · level 0 · unverified · bec6363e2390b390
  2. BetaVAE_MLP helper · level 1 · ran · d4fd240849acc2b3
  3. Inference helper · level 1 · ran · 773460f058b3b35c
  4. MBDTransitionPrior model · level 1 · ran · 99f55689f9c969b1
  5. MLPDecoder helper · level 1 · ran · d6c09b008d2e8fe3
  6. MLPEncoder helper · level 1 · ran · bfc5af9d3691e10d
  7. NPTransitionPrior model · level 1 · ran · bdecb548777436c9
  8. compute_mcc helper · level 0 · unverified · 0b6abb112159adb6
  9. correlation helper · level 0 · unverified · 228dbb5491c93115
  10. kaiming_init helper · level 0 · unverified · a18c3595f7425f34
  11. reparametrize helper · level 1 · ran · honoured contract · 863fc64cd51264f0
  12. NLayerLeakyMLP helper · level 1 · ran · c4c2e657dc649aae
  13. GroupLinearLayer helper · level 1 · ran · 3afb21c8fdb93144
  14. Munkres helper · level 0 · unverified · 490d0594e6f6579c
  15. make_cost_matrix helper · level 1 · ran · our draft was wrong · 60f32cea809132df

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="2401.14535") returns these assemblies with each brick's role and wiring (how to connect).

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