Papers › TraCE: Trajectory Counterfactual Explanation Scores

TraCE: Trajectory Counterfactual Explanation Scores

27 Sep 2023arXiv:2309.15965archive 2025-07-28

Jeffrey N. Clark, Edward A. Small, Nawid Keshtmand, Michelle W. L. Wan, Elena Fillola Mayoral, Enrico Werner, Christopher P. Bourdeaux, Raul Santos-Rodriguez

Counterfactual explanations, and their associated algorithmic recourse, are typically leveraged to understand, explain, and potentially alter a prediction coming from a black-box classifier. In this paper, we propose to extend the use of counterfactuals to evaluate progress in sequential decision making tasks. To this end, we introduce a model-agnostic modular framework, TraCE (Trajectory Counterfactual Explanation) scores, which is able to distill and condense progress in highly complex scenarios into a single value. We demonstrate TraCE's utility across domains by showcasing its main properties in two case studies spanning healthcare and climate change.

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

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

jeffnclark/trace officialmentioned in paperApache-2.0Syntology: 14 samples, 9 ran (0 instrument-failed) · 5 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

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

9ran
5unverified

Licence: 0 of the 14 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 jeffnclark/trace. “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.

jeffnclark/trace official repository 14 samples, 9 ran (0 instrument-failed) · 5 unverified
change_categorical helpers/funcs_icu_study.py ran Apache-2.0 (permissive) · 0ce50857b146ff6e · report fixture: signature df:DataFrame/0/?, categorical_features:list/1/str · returned DataFrame · level recorded 2026-09-24
cos_sim in 34 papers
census: 5 implementations from 5 papers, 4 distinct outputs across 3 buckets, one shared input per bucket
helpers/funcs.py ran fingerprinted Apache-2.0 (permissive) · bff9357caec21792 · report fixture: signature v:ndarray/1/float, u:ndarray/1/float · returned float64 · level recorded 2026-09-24
n_sphere helpers/funcs.py ran fingerprinted Apache-2.0 (permissive) · 9c7a8779b32dbd02 · report fixture: signature v:ndarray/1/float · returned float64 · level recorded 2026-09-24
nan_post_processing_data helpers/funcs_icu_study.py ran Apache-2.0 (permissive) · 8dcf34339f3961ce · report fixture: signature df_data:DataFrame/0/?, columns:list/1/str · returned DataFrame · level recorded 2026-09-24
obtain_stay_id_individuals ICU_TraCE_scores.py ran Apache-2.0 (permissive) · 51e1fcbf1e618076 · report fixture: signature data:DataFrame/0/?, labels:DataFrame/0/?, label_value:int/0/int · returned DataFrame · level recorded 2026-09-24
plot_dataset helpers/plotters.py ran Apache-2.0 (permissive) · f6e80cda9b180e6d · report fixture: signature ax:Axes/0/?, df:DataFrame/0/?, size:int/0/int · returned Axes · level recorded 2026-09-24
plot_decision_boundary helpers/plotters.py ran Apache-2.0 (permissive) · bb274893d5e95c1a · report fixture: signature ax:Axes/0/?, X_scaled:ndarray/2/float, predictor:SimplePredictor/0/?, color_bar:bool/0/bool, levels:int/0/int, alpha:float/0/float · returned Axes · level recorded 2026-09-24
plot_density helpers/plotters.py ran Apache-2.0 (permissive) · 6377a0fb1f97b336 · report fixture: signature ax:Axes/0/?, X_scaled:ndarray/2/float, dense:EllipticEnvelope/0/?, color_bar:bool/0/bool, levels:int/0/int, alpha:float/0/float, over:bool/0/bool · returned Axes · level recorded 2026-09-24
vec helpers/funcs.py ran fingerprinted Apache-2.0 (permissive) · ffa2aada7cc61d14 · report fixture: signature x1:Tensor/2/float, x2:Tensor/2/float · returned Tensor · level recorded 2026-09-24
cf_generator helpers/funcs_icu_study.py unverified Apache-2.0 (permissive) · ecef3ab232914eb3 · report
convert_nc_to_csv helpers/funcs_ssp_study.py unverified Apache-2.0 (permissive) · e31cd68943331ac1 · report
generate_dice_cf_global ICU_TraCE_scores.py unverified Apache-2.0 (permissive) · 9d32e662b0e911b9 · report
merge_exp_versions helpers/funcs_ssp_study.py unverified Apache-2.0 (permissive) · 53fb628bd87a789a · report
train_classifier in 11 papers ICU_TraCE_scores.py unverified Apache-2.0 (permissive) · 2080bccdc34c542c · report

Tasks

Counterfactual ExplanationDecision MakingSequential Decision Making

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

Counterfactuals

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