Maarten Buyl, Marybeth Defrance, Tijl De Bie
1 of 1 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, 0 violated it and 0 have no contract verdict; 1 failure of our instrument; 0 no recorded run), measured 2026-11-22; 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/2409.16965.json · badge: /api/ran/2409.16965.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 |
|---|---|---|
| aida-ugent/abcfair | canonical (classifier label) classifier basis: census |
1 ran · 0 no recorded run |
| Function | Status | Where it lives |
|---|---|---|
| performance_evaluator | Ran ran; our contract draft was wrong, not the code |
aida-ugent/abcfair/src/evaluator/evaluator.py pointer only (licence: NONE) · get_code("26746ed0265bdb1a") How it ranThe body of this sample is withheld: GitHub detected no licence in this paper's repository, aida-ugent/abcfair 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. |
Of 1 samples lifted from this paper's linked repositories, 1 carry a function identity and 0 do not. Of the 1 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 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.
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.
Numerous methods have been implemented that pursue fairness with respect to sensitive features by mitigating biases in machine learning. Yet, the problem settings that each method tackles vary significantly, including the stage of intervention, the composition of sensitive features, the fairness notion, and the distribution of the output. Even in binary classification, these subtle differences make it highly complicated to benchmark fairness methods, as their performance can strongly depend on exactly how the bias mitigation problem was originally framed. Hence, we introduce ABCFair, a benchmark approach which allows adapting to the desiderata of the real-world problem setting, enabling proper comparability between methods for any use case. We apply ABCFair to a range of pre-, in-, and postprocessing methods on both large-scale, traditional datasets and on a dual label (biased and unbiased) dataset to sidestep the fairness-accuracy trade-off. Contributions. We formalize four types of desiderata that could arise in real-world classification problems. These include 1) the stage where the method intervenes, 2) the composition of sensitive groups, 3) the exact definition of fairness, and 4) the distribution that is expected from the model output. Figure 1 shows where these desiderata pose comparability challenges in a fairness pipeline. We introduce ABCFair: an adaptable benchmark approach for comparing fairness methods. Through the use of three flexible components, the Data, FairnessMethod, and Evaluator, it can adapt to a range of desiderata imposed by the task. The approach is validated by benchmarking it on 10 methods, 7 fairness notions, 3 formats of sensitive features, and 2 output distribution formats. Preprint. Under review.
The same record, over MCP at https://syntology.ai/mcp:
get_harvested_code_for_paper("2409.16965")
get_code_for_paper("2409.16965")
have("2409.16965")
The run record, dated, one paper per request, free:
curl https://syntology.ai/api/ran/2409.16965.json
A badge for a README (the split and the date, never a ratio):
[](https://syntology.ai/paper/2409.16965)
Connect an agent — have() is free.