SYNTOLOGY HomeExplorerAtlasCodeMethodologyAboutDevelopersFeedPricing
Paper · 2107.05913 · NeurIPS · 2021

Can Less be More? When Increasing-to-Balancing Label Noise Rates Considered Beneficial

Yang Liu, Jialu Wang

arXiv · PDF · Open in the Atlas

Code that ran

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, 0 violated it and 0 have no contract verdict; 3 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/2107.05913.json · badge: /api/ran/2107.05913.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.

RepositoryRoleRan
ucsc-real/canlessbemore canonical (classifier label)
classifier basis: classifier_2025
3 ran · 2 no recorded run
FunctionStatusWhere it lives
calculate_agreement_difference Ran
ran; our contract draft was wrong, not the code
ucsc-real/canlessbemore/CanLessBeMore.py
pointer only (licence: NONE) · get_code("3156bb4fd3e3e8b6")
How it ran

The body of this sample is withheld: GitHub detected no licence in this paper's repository, ucsc-real/canlessbemore 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.

count_agreement Ran
ran; the contract check could not run (RAISES, DEP_MISSING or TIMEOUT)
ucsc-real/canlessbemore/CanLessBeMore.py
pointer only (licence: NONE) · get_code("0b53eb06f1c7b157")
How it ran

The body of this sample is withheld: GitHub detected no licence in this paper's repository, ucsc-real/canlessbemore 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.

increase_noise Ran
ran; the contract check could not run (RAISES, DEP_MISSING or TIMEOUT)
ucsc-real/canlessbemore/CanLessBeMore.py
pointer only (licence: NONE) · get_code("877d996dea33b4e0")
How it ran

The body of this sample is withheld: GitHub detected no licence in this paper's repository, ucsc-real/canlessbemore 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.

monoflip Not yet run
unverified (harvested, no recorded run)
ucsc-real/canlessbemore/CanLessBeMore.py
pointer only (licence: NONE) · get_code("293f09e93f5e3926")
How it ran

The body of this sample is withheld: GitHub detected no licence in this paper's repository, ucsc-real/canlessbemore 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.

tune_balance Not yet run
unverified (harvested, no recorded run)
ucsc-real/canlessbemore/CanLessBeMore.py
pointer only (licence: NONE) · get_code("ca3bd0d3659af2aa")
How it ran

The body of this sample is withheld: GitHub detected no licence in this paper's repository, ucsc-real/canlessbemore 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.

Also present in other papers' code

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.

Repositories linked to this paper

Some links come from the archived Papers with Code dataset (CC BY-SA 4.0): attribution and licence.

Abstract

In this paper, we answer the question of when inserting label noise (less informative labels) can instead return us more accurate and fair models. We are primarily inspired by three observations: 1) In contrast to reducing label noise rates, increasing the noise rates is easy to implement; 2) Increasing a certain class of instances' label noise to balance the noise rates (increasing-to-balancing) results in an easier learning problem; 3) Increasing-to-balancing improves fairness guarantees against label bias. In this paper, we first quantify the trade-offs introduced by increasing a certain group of instances' label noise rate w.r.t. the loss of label informativeness and the lowered learning difficulties. We analytically demonstrate when such an increase is beneficial, in terms of either improved generalization power or the fairness guarantees. Then we present a method to insert label noise properly for the task of learning with noisy labels, either without or with a fairness constraint. The primary technical challenge we face is due to the fact that we would not know which data instances are suffering from higher noise, and we would not have the ground truth labels to verify any possible hypothesis. We propose a detection method that informs us which group of labels might suffer from higher noise without using ground truth labels. We formally establish the effectiveness of the proposed solution and demonstrate it with extensive experiments.

For agents

The same record, over MCP at https://syntology.ai/mcp:

get_harvested_code_for_paper("2107.05913")
get_code_for_paper("2107.05913")
have("2107.05913")

The run record, dated, one paper per request, free:

curl https://syntology.ai/api/ran/2107.05913.json

A badge for a README (the split and the date, never a ratio):

[![Syntology run record](https://syntology.ai/api/ran/2107.05913.svg)](https://syntology.ai/paper/2107.05913)

Connect an agent — have() is free.