Papers › A comparative study of fairness-enhancing interventions in machine learning

A comparative study of fairness-enhancing interventions in machine learning

13 Feb 2018arXiv:1802.04422archive 2025-07-28

Sorelle A. Friedler, Carlos Scheidegger, Suresh Venkatasubramanian, Sonam Choudhary, Evan P. Hamilton, Derek Roth

Computers are increasingly used to make decisions that have significant impact in people's lives. Often, these predictions can affect different population subgroups disproportionately. As a result, the issue of fairness has received much recent interest, and a number of fairness-enhanced classifiers and predictors have appeared in the literature. This paper seeks to study the following questions: how do these different techniques fundamentally compare to one another, and what accounts for the differences? Specifically, we seek to bring attention to many under-appreciated aspects of such fairness-enhancing interventions. Concretely, we present the results of an open benchmark we have developed that lets us compare a number of different algorithms under a variety of fairness measures, and a large number of existing datasets. We find that although different algorithms tend to prefer specific formulations of fairness preservations, many of these measures strongly correlate with one another. In addition, we find that fairness-preserving algorithms tend to be sensitive to fluctuations in dataset composition (simulated in our benchmark by varying training-test splits), indicating that fairness interventions might be more brittle than previously thought.

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 11 code samples harvested from 4 repositories linked to this paper: 10 ran (of which 0 constructed an object rather than computing a result; 1 with no instrument failure: 1 honoured, 0 violated, 0 with no contract checked; 9 where Syntology's instrument failed) · 1 unverified. Where Syntology's instrument failed: 9 where our contract draft was wrong; failures of Syntology's instrument, not of the code.

By repository: official repository: 4 samples from 1 repository, 4 ran (0 with no instrument failure; 4 where Syntology's instrument failed); community (archive-listed): 7 samples from 3 repositories, 6 ran (1 with no instrument failure; 5 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-22 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

algofairness/fairness-comparison officialmentioned in papermentioned on GitHubSyntology: 4 samples, 4 ran (4 instrument-failed) · 0 unverified report
JSGoedhart/fairness-comparison mentioned on GitHubSyntology: 2 samples, 2 ran (2 instrument-failed) · 0 unverified report
charan223/FairDeepLearning mentioned on GitHubpytorchSyntology: 4 samples, 3 ran (3 instrument-failed) · 1 unverified report
huanglx12/Stable-Fair-Classification mentioned on GitHubSyntology: 1 sample, 1 ran (0 instrument-failed) · 0 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

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

1ran · honoured contract
9ran · our draft was wrong
1unverified

Licence: 7 of the 11 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 4 repositories linked to this paper, official or community; the list below is grouped by repository, each group headed by its name and what it is to the paper. “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.

algofairness/fairness-comparison official repository 4 samples, 4 ran (4 instrument-failed) · 0 unverified
get_dict_sensitive_vals fairness/benchmark.py ran · our draft was wrong licence not identified · pointer only · 6642c1dab7b8e92b · report fixture: signature dict_sensitive_lists:dict/0/? · returned dict · level recorded 2026-09-22
get_sensitive_from_filename analysis/correlation-vis/combine_results_files.py ran · our draft was wrong licence not identified · pointer only · 0f5b147fa50f6183 · report fixture: signature filename:str/0/str · returned tuple · level recorded 2026-09-22
make_metrics_list analysis/correlation-vis/combine_results_files.py ran · our draft was wrong fingerprinted licence not identified · pointer only · 91ce47d82c73659b · report fixture: signature sensitive_attr:str/0/str · returned list · level recorded 2026-09-22
run_alg fairness/benchmark.py ran · our draft was wrong licence not identified · pointer only · 5bd1ce1fcaa81378 · report fixture: signature algorithm:MockAlgorithm/0/?, train:list/1/tuple, test:list/1/tuple, dataset:MockDataset/0/?, all_sensitive_attributes:list/1/str, single_sensitive:str/0/str, privileged_vals:dict/0/?, positive_val:int/0/int · returned tuple · level recorded 2026-09-22
JSGoedhart/fairness-comparison community (archive-listed) 2 samples, 2 ran (2 instrument-failed) · 0 unverified
all_possible_graphs fairness/analysis.py ran · our draft was wrong licence not identified · pointer only · a8410405c788323a · report fixture: signature f:DataFrame/0/? · returned list · level recorded 2026-09-22
run_alg fairness/benchmark.py ran · our draft was wrong licence not identified · pointer only · 13d270541da56dd7 · report fixture: signature algorithm:MockAlgorithm/0/?, train:list/1/tuple, test:list/1/tuple, dataset:MockDataset/0/?, all_sensitive_attributes:list/1/str, single_sensitive:str/0/str, privileged_vals:dict/0/?, positive_val:int/0/int · returned tuple · level recorded 2026-09-22
charan223/FairDeepLearning community (archive-listed) 4 samples, 3 ran (3 instrument-failed) · 1 unverified
filter_table scripts/plots_tables/csvs/parse_csv.py ran · our draft was wrong MIT (permissive) · 7da718e0807f10c7 · report fixture: signature data_table:DataFrame/0/?, metric_cols:dict/0/?, all_grouping_cols:list/1/str · returned DataFrame · level recorded 2026-09-22
get_iters train/execute.py ran · our draft was wrong MIT (permissive) · c861a2f90457c10b · report fixture: signature args:MockArgs/0/?, dataset:MockDataset/0/? · returned tuple · level recorded 2026-09-22
group_and_agg scripts/plots_tables/csvs/parse_csv.py ran · our draft was wrong MIT (permissive) · a6f24b46ffb7aa43 · report fixture: signature tbl:DataFrame/0/?, mean_grouping_cols:list/1/str, metric_cols:dict/0/? · returned tuple · level recorded 2026-09-22
group_and_max scripts/plots_tables/csvs/parse_csv.py unverified MIT (permissive) · 37de72ff09213994 · report
huanglx12/Stable-Fair-Classification community (archive-listed) 1 sample, 1 ran (0 instrument-failed) · 0 unverified
compute_diff_nums fairness/benchmark.py ran · honoured contract no licence file found · pointer only · 47a0278c9fef3265 · report fixture: signature predictions:list/1/list · returned int · level recorded 2026-09-22

Tasks

BIG-bench Machine LearningFairness

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

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