Papers › Federated Causal Discovery from Heterogeneous Data
Federated Causal Discovery from Heterogeneous Data
Loka Li, Ignavier Ng, Gongxu Luo, Biwei Huang, Guangyi Chen, Tongliang Liu, Bin Gu, Kun Zhang
Conventional causal discovery methods rely on centralized data, which is inconsistent with the decentralized nature of data in many real-world situations. This discrepancy has motivated the development of federated causal discovery (FCD) approaches. However, existing FCD methods may be limited by their potentially restrictive assumptions of identifiable functional causal models or homogeneous data distributions, narrowing their applicability in diverse scenarios. In this paper, we propose a novel FCD method attempting to accommodate arbitrary causal models and heterogeneous data. We first utilize a surrogate variable corresponding to the client index to account for the data heterogeneity across different clients. We then develop a federated conditional independence test (FCIT) for causal skeleton discovery and establish a federated independent change principle (FICP) to determine causal directions. These approaches involve constructing summary statistics as a proxy of the raw data to protect data privacy. Owing to the nonparametric properties, FCIT and FICP make no assumption about particular functional forms, thereby facilitating the handling of arbitrary causal models. We conduct extensive experiments on synthetic and real datasets to show the efficacy of our method. The code is available at https://github.com/lokali/FedCDH.git.
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.
Syntology holds a reference implementation of Federated Causal Discovery (FCD) method, generated from the paper text (not the authors' code), at level 2 on Syntology's ladder: V2 “two implementations GENERATED from the paper's signature and spec agree numerically (1e-6) on fixture inputs” “neither of the two ever read the authors' own code, so V2 measures how unambiguously the paper specifies the method, not fidelity to the authors' implementation (measured 2026-09-11, commit 75eaa77: cross_checked_by is a second LLM on 2,628 of 2,831 served samples)” (quoted from Syntology's server card). No rung compares this code against the authors' implementation. For agents: get_reference_implementation(name='Federated Causal Discovery (FCD) method') (how to connect); the free check have('2402.13241') needs no token.
For agents, on Syntology's MCP service (how to connect):
get_harvested_code_for_paper(arxiv_id="2402.13241")get_code(code_sha256="…")with a sample'scode_sha256from the list belowget_citation_path(paper_1="2402.13241", paper_2="…")with another paper's arXiv id or titleget_concepts_for_paper(arxiv_id="2402.13241")
Code
Syntology 19 code samples harvested from 1 repository linked to this paper: 10 ran (of which 1 constructed an object rather than computing a result; 7 with no instrument failure: 3 honoured, 1 violated, 3 with no contract checked; 3 where Syntology's instrument failed) · 9 unverified. Where Syntology's instrument failed: 1 where our contract draft was wrong; 2 where the contract check could not run; failures of Syntology's instrument, not of the code.
By repository: official repository: 19 samples from 1 repository, 10 ran (7 with no instrument failure; 3 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-26 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.
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
19 samples harvested: 10 ran (of which 1 constructed an object rather than computing a result; 7 with no instrument failure: 3 honoured, 1 violated, 3 with no contract checked; 3 where Syntology's instrument failed) · 9 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.
Licence: 19 of the 19 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 lokali/fedcdh. “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. 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.
38976b280ca96d56 · report
fixture: returned BootstrapResult · level recorded 2026-09-22 491a78ded363ffcf · report
fixture: signature X:ndarray/2/float, n_sampling:int/0/int · returned BootstrapResult · level recorded 2026-09-24 26b76c70199f57dc · report
fixture: signature X:ndarray/2/float, width:float/0/float · returned ndarray · level recorded 2026-09-22 e5a1aadd816748c7 · report
fixture: signature dag:ndarray/2/float, from_index:int/0/int, to_index:int/0/int, min_causal_effect:float/0/float · returned tuple · level recorded 2026-09-22 census: 1 implementation from 5 papers, 1 distinct output on one shared input causallearn/search/FCMBased/lingam/multi_group_direct_lingam.py ran · honoured contract fingerprinted no licence file found · pointer only ·
1771651b948f9b7b · report
fixture: signature X:ndarray/2/float, width:float/0/float · returned tuple · level recorded 2026-09-22 976bd4440dd93c4a · report
fixture: signature X:ndarray/2/float · returned float64 · level recorded 2026-09-22 bbe022bdabc2d20d · report
fixture: signature X:ndarray/2/float, Y:ndarray/2/float, bw_method:str/0/str · returned tuple · level recorded 2026-09-22 9a331c08a7211248 · report
fixture: signature Kc:ndarray/2/float, Lc:ndarray/2/float, n:float/0/float · returned float64 · level recorded 2026-09-22 d6e616a314e0694d · report
fixture: signature edge:Edge/0/?, z:str/0/str, end:str/0/str · returned bool · level recorded 2026-09-26 25ba4d6c123c8516 · report
fixture: signature X:ndarray/2/float, predictors:ndarray/1/int, target:int/0/int, gamma:float/0/float · returned ndarray · level recorded 2026-09-22 38543c5552e0b75d · report
6cd2527abc81e1b4 · report
99dc4a93f1437f57 · report
7686f7904ef2a421 · report
98df2a458d28d6c9 · report
d42a8602e0bd67de · report
1b53b842af405e31 · report
f373e8a4a7fc7f4e · report
c5559d99b5cf2bf8 · 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. For a generated assembly, an independent peer is a second implementation generated separately from the same paper text; neither implementation read the authors' code. At level 2 the two agreed numerically on the fixture's inputs; level 3 is recorded when property tests derived from the paper also passed on both, and each level 3 card prints how many its report lists. 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. A generated assembly's label was set when its code was generated for the method, and no model judged it; its card prints it as "by construction" or "not judged by a model". Where an assembly's phrase has no constructed figure, a brick that ran is not among the harvested samples this build reads, and whether a brick's run only constructed an object is read from that brick's harvested sample, so the figure was not counted; it does not say there were none.
2 assemblies on this paper: 1 harvested, 1 generated.
generated Assembly for Federated Causal Discovery (FCD) method (graph method: Federated Causal Discovery (FCD) method), generated from the paper text, not the repository's code. 1 brick; individually on a fixture: 1 ran (1 with no instrument failure: 0 honoured, 0 violated, 1 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified. Ran end-to-end against an independent peer (level 2).
label matches by construction: the code was generated for this method (not judged by a model)
- federated_covariance_aggregation entry · level 2 · ran ·
da47ad649a9b39b57de8dc77ac262436e0473b2373ad38d84b97c45ce99e7fb1
harvested Assembly for Federated Causal Discovery (FCD) method (graph method: Federated Causal Discovery (FCD) method). 12 bricks; individually on a fixture: 9 ran (of which 1 constructed an object rather than computing a result; 6 with no instrument failure: 3 honoured, 1 violated, 2 with no contract checked; 3 where Syntology's instrument failed) · 3 unverified. The assembly has not been run end-to-end.
- MultiGroupDirectLiNGAM entry · level 0 · unverified ·
6cd2527abc81e1b4 - BootstrapResult helper · level 1 · ran ·
38976b280ca96d56 - DirectLiNGAM model · level 1 · ran ·
491a78ded363ffcf - hsic_test_gamma helper · level 1 · ran; the contract check could not run (RAISES) ·
bbe022bdabc2d20d - predict_adaptive_lasso helper · level 1 · ran; the contract check could not run (RAISES) ·
25ba4d6c123c8516 - find_all_paths helper · level 1 · ran · our draft was wrong ·
e5a1aadd816748c7 - _BaseLiNGAM model · level 0 · unverified ·
99dc4a93f1437f57 - get_gram_matrix helper · level 1 · ran · honoured contract ·
1771651b948f9b7b - get_kernel_width helper · level 1 · ran · honoured contract ·
976bd4440dd93c4a - hsic_teststat helper · level 1 · ran · violated contract ·
9a331c08a7211248 - BootstrapMixin helper · level 0 · unverified ·
38543c5552e0b75d - _rbf_dot_XX helper · level 1 · ran · honoured contract ·
26b76c70199f57dc
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="2402.13241") returns these assemblies with each brick's role and wiring (how to connect).
Tasks
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