REVIEW 2 cited by
gCastle: A Python Toolbox for Causal Discovery
Not yet reviewed by Pith; the record is open.
This paper has not been read by Pith yet. Machine review is queued; the pith claim, tier, and objections will appear here once it completes.
SPECIMEN: schema-true, not a live event
T0 review · schema-true
One-sentence machine reading of the paper's core claim.
pith:XXXXXXXX · record.json · timestamp
abstract
$\texttt{gCastle}$ is an end-to-end Python toolbox for causal structure learning. It provides functionalities of generating data from either simulator or real-world dataset, learning causal structure from the data, and evaluating the learned graph, together with useful practices such as prior knowledge insertion, preliminary neighborhood selection, and post-processing to remove false discoveries. Compared with related packages, $\texttt{gCastle}$ includes many recently developed gradient-based causal discovery methods with optional GPU acceleration. $\texttt{gCastle}$ brings convenience to researchers who may directly experiment with the code as well as practitioners with graphical user interference. Three real-world datasets in telecommunications are also provided in the current version. $\texttt{gCastle}$ is available under Apache License 2.0 at \url{https://github.com/huawei-noah/trustworthyAI/tree/master/gcastle}.
Forward citations
Cited by 2 Pith papers
-
AutoCause: A Python framework that automates expert decisions in environmental time-series causal discovery
An auditable consensus workflow around four causal-discovery methods gives higher-precision links on synthetic benchmarks, but the precision gain disappears on a real river network where the reference graph is incomplete.
-
Causal Explainability of Machine Learning in Heart Failure Prediction from Electronic Health Records
A neural-net-transformed disease label is fed into causal discovery, and the resulting 'causal strength' ranks are compared with ML feature importance on heart failure EHR data, with the comparison likely inflated by ...
Discussion (0). Continue with ORCID to comment.