Romain Hennequin, Darius Afchar, Vincent Guigue
3 of 5 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 2 have no contract verdict; 0 failures of our instrument; 2 no recorded run), 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/2104.12437.json · badge: /api/ran/2104.12437.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 |
|---|---|---|
| deezer/functional_attribution | canonical (classifier label) classifier basis: classifier_2025 |
3 ran · 2 no recorded run |
| Function | Status | Where it lives |
|---|---|---|
| Explainer | Ran ran on a synthesized input |
deezer/functional_attribution/methods.py pointer only (licence: NONE) · get_code("f694313af6e1b67f") How it ranThe body of this sample is withheld: GitHub detected no licence in this paper's repository, deezer/functional_attribution 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. |
| binarise_subset | Ran ran, violated the contract we drafted |
deezer/functional_attribution/methods.py pointer only (licence: NONE) · get_code("8e5ad69ba70d09bb") How it ranThe body of this sample is withheld: GitHub detected no licence in this paper's repository, deezer/functional_attribution 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. |
| fANOVA | Ran ran on a synthesized input |
deezer/functional_attribution/methods.py pointer only (licence: NONE) · get_code("a95f1435c6b35e74") How it ranThe body of this sample is withheld: GitHub detected no licence in this paper's repository, deezer/functional_attribution 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. |
| bit_count | Not yet run unverified (harvested, no recorded run) |
deezer/functional_attribution/methods.py pointer only (licence: NONE) · get_code("56152d100944aeff") How it ranThe body of this sample is withheld: GitHub detected no licence in this paper's repository, deezer/functional_attribution 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. |
| has_k_el | Not yet run unverified (harvested, no recorded run) |
deezer/functional_attribution/methods.py pointer only (licence: NONE) · get_code("a210e7c1f82f5928") How it ranThe body of this sample is withheld: GitHub detected no licence in this paper's repository, deezer/functional_attribution 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 5 samples lifted from this paper's linked repositories, 5 carry a function identity and 0 do not. Of the 5 distinct functions with an identity, 0 are also present in other papers whose code we hold (0 with at least one paper dated earlier, 0 the same month, 0 later) and 5 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.
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.
Feature attribution is often loosely presented as the process of selecting a subset of relevant features as a rationale of a prediction. Taskdependent by nature, precise definitions of "relevance" encountered in the literature are however not always consistent. This lack of clarity stems from the fact that we usually do not have access to any notion of ground-truth attribution and from a more general debate on what good interpretations are. In this paper we propose to formalise feature selection/attribution based on the concept of relaxed functional dependence. In particular, we extend our notions to the instance-wise setting and derive necessary properties for candidate selection solutions, while leaving room for task-dependence. By computing ground-truth attributions on synthetic datasets, we evaluate many state-of-the-art attribution methods and show that, even when optimised, some fail to verify the proposed properties and provide wrong solutions. This may explain why many methods have resorted to proxy measures of interpretability and have proposed list of general requirements for interpretations -e.g.
The same record, over MCP at https://syntology.ai/mcp:
get_harvested_code_for_paper("2104.12437")
get_code_for_paper("2104.12437")
have("2104.12437")
The run record, dated, one paper per request, free:
curl https://syntology.ai/api/ran/2104.12437.json
A badge for a README (the split and the date, never a ratio):
[](https://syntology.ai/paper/2104.12437)
Connect an agent — have() is free.