Rahul Sharma, Sebastian Vollmer, Sumantrak Mukherjee, Andrea Šipka, Eyke Üllermeier, Sergey Redyuk, David Selby, David Antony, Selby Antony
1 of 2 samples (functions and classes) lifted from this paper's linked repositories executed on a synthesized input in Syntology's jail (0 of them constructed an object rather than computing a result; 0 honoured the contract we drafted, 1 violated it and 0 have no contract verdict; 0 failures of our instrument; 1 no recorded run); 1 of them was also run on the host, not in the jail, by the peer-agreement lane that set its level, measured 2026-11-22; repository links from the Papers with Code archive attributed under CC BY-SA, no affiliation; bodies inline only under a permissive licence as GitHub detects it. Not a reproduction of the paper's results.
"Ran" means the function executed on a synthesized input and returned a value. It is not a reproduction of the paper's results. This record, dated, as JSON: /api/ran/2401.08513.json · badge: /api/ran/2401.08513.svg
Each repository's role is a label: a classifier's output recorded on the link, or, where no role is recorded, what the Papers with Code archive marked. The line under it names its basis. Neither says who wrote the code.
| Repository | Role | Ran |
|---|---|---|
| selbosh/p-hacking | canonical (classifier label) classifier basis: census |
1 ran · 1 no recorded run |
| Function | Status | Where it lives |
|---|---|---|
| sigmoid | Ran ran, violated the contract we drafted |
selbosh/p-hacking/src/rahulsStuff/experiments/source/graphs.py pointer only (licence: NONE) · get_code("b8e95809ca2c17c9") How it ranThe body of this sample is withheld: GitHub detected no licence in this paper's repository, selbosh/p-hacking when it was checked. The setup block that called it is withheld with it, because it is written against that body. source_path and origin say where the code lives, to read under the repository's own terms. A run is recorded. |
| plot_subgraphs | Not yet run unverified (harvested, no recorded run) |
selbosh/p-hacking/src/rahulsStuff/experiments/source/graphs.py pointer only (licence: NONE) · get_code("e749726defb2cb03") How it ranThe body of this sample is withheld: GitHub detected no licence in this paper's repository, selbosh/p-hacking when it was checked. The setup block that called it is withheld with it, because it is written against that body. source_path and origin say where the code lives, to read under the repository's own terms. No invocation recorded. |
Of 2 samples lifted from this paper's linked repositories, 2 carry a function identity and 0 do not. Of the 2 distinct functions with an identity, 1 are also present in other papers whose code we hold (1 with at least one paper dated earlier, 1 the same month, 1 later) and 1 are only here among the 52,977 papers whose code Syntology holds (as of 2026-09-26).
Only here means: among the 52,977 papers whose code Syntology holds (51,887 with lifted samples, 1,090 through their assemblies only), as of 2026-09-26, no other paper's lifted samples or current assembly bricks contain an identical function body after normalisation.
| Function | Also present in | Earliest-dated | Others named |
|---|---|---|---|
| sigmoid | 51 other papers 36 dated earlier, 1 the same month, 14 later · 2 only as an assembly brick |
1505.05770 (2015-05) Variational Inference with Normalizing Flows |
1804.00779 (2018-04) Neural Autoregressive Flows 1809.10765 (2018-09) Auto-Encoding Knockoff Generator for FDR Controlled Variable Selection and 48 more not named here |
Presence, not direction: an identical function body in two papers' repositories does not say who wrote it, which came from which, or that either paper's method rests on it. Matching is exact after normalisation, so a renamed or edited function is not matched. Dates are when papers appeared, not when code was written. Only .py files the harvester lifted are covered; notebooks are not read. A new-style arXiv id YYMM.NNNN dates a paper to the month 20YY-MM; otherwise Paper.year dates it to the year; otherwise it is undated. Dates are when the paper appeared, not when the code was written. Read 2026-11-22.
Some links come from the archived Papers with Code dataset (CC BY-SA 4.0): attribution and licence.
Explainable AI (XAI) and interpretable machine learning methods help to build trust in model predictions and derived insights, yet also present a perverse incentive for analysts to manipulate XAI metrics to support pre-specified conclusions. This paper introduces the concept of X-hacking, a form of p-hacking applied to XAI metrics such as SHAP values. We show how easily an automated machine learning pipeline can be adapted to exploit model multiplicity at scale: searching a Rashomon set of 'defensible' models with similar predictive performance to find a desired explanation. We formulate the trade-off between explanation and accuracy as a multi-objective optimisation problem, and illustrate empirically on familiar real-world datasets that, on average, Bayesian optimisation accelerates X-hacking 3-fold for features susceptible to it, versus random sampling. We show the vulnerability of a dataset to X-hacking can be determined by information redundancy among features. Finally, we suggest possible methods for detection and prevention, and discuss ethical implications for the credibility and reproducibility of XAI.
The same record, over MCP at https://syntology.ai/mcp:
get_harvested_code_for_paper("2401.08513")
get_code_for_paper("2401.08513")
have("2401.08513")
The run record, dated, one paper per request, free:
curl https://syntology.ai/api/ran/2401.08513.json
A badge for a README (the split and the date, never a ratio):
[](https://syntology.ai/paper/2401.08513)
Connect an agent — have() is free.