Papers › Theoretically Principled Trade-off between Robustness and Accuracy

Theoretically Principled Trade-off between Robustness and Accuracy

24 Jan 2019arXiv:1901.08573archive 2025-07-28

Hongyang Zhang, Yaodong Yu, Jiantao Jiao, Eric P. Xing, Laurent El Ghaoui, Michael. I. Jordan

We identify a trade-off between robustness and accuracy that serves as a guiding principle in the design of defenses against adversarial examples. Although this problem has been widely studied empirically, much remains unknown concerning the theory underlying this trade-off. In this work, we decompose the prediction error for adversarial examples (robust error) as the sum of the natural (classification) error and boundary error, and provide a differentiable upper bound using the theory of classification-calibrated loss, which is shown to be the tightest possible upper bound uniform over all probability distributions and measurable predictors. Inspired by our theoretical analysis, we also design a new defense method, TRADES, to trade adversarial robustness off against accuracy. Our proposed algorithm performs well experimentally in real-world datasets. The methodology is the foundation of our entry to the NeurIPS 2018 Adversarial Vision Challenge in which we won the 1st place out of ~2,000 submissions, surpassing the runner-up approach by 11.41% in terms of mean ℓ₂ perturbation distance.

PaperPDFCodeCode Syntology ran

In Syntology Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, Syntology's MCP tool lists every function and class Syntology harvested from this paper and whether it ran (how to connect): get_harvested_code_for_paper(arxiv_id="1901.08573")

Code

Syntology Ran 12 of 15 code samples harvested from 5 repositories linked to this paper; 3 have no recorded run. Of those that ran: 4 ran · our draft was wrong; 1 ran · fixture could not drive it; 7 ran with no contract checked.

By repository: community (archive-listed): 13 samples from 5 repositories, 11 ran; 2 identical to code first harvested elsewhere. The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

yaodongyu/TRADES officialmentioned in papermentioned on GitHubpytorch report
TonyYaoMSU/TRADES mentioned on GitHubpytorch report
arobey1/advbench mentioned on GitHubpytorch report
goldblum/AdversariallyRobustDistillation mentioned on GitHubpytorchMIT report
nutellamok/advrush mentioned on GitHubpytorch report
val-iisc/flss mentioned on GitHubpytorch report
zjfheart/Friendly-Adversarial-Training mentioned on GitHubpytorch 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

15 samples harvested; 12 ran; 0 honoured the contract we drafted; 3 have no recorded run. Read from Syntology's graph 2026-09-24; that is when this build read the record, not when the samples ran.

4ran · our draft was wrong
1ran · fixture could not drive it
7ran
3unverified

Licence: 4 of the 15 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 5 repositories linked to this paper, official or community; each sample names its own and says which. Some samples are identical code Syntology first harvested from another repository; for those, this paper's copy is not located and its licence is not recorded. “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. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself; “our draft was wrong” and “fixture could not drive it” are failures of Syntology's instrument, not of the code.

Each sample ends with its code_sha256, Syntology's identity for that exact code. An agent fetches the stored sample with Syntology's MCP tool get_code(code_sha256="…") (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 from a repository marked official are listed first. 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 four 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; or the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar). 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.

Attack arobey1/advbench/advbench/algorithms.py community (archive-listed) ran MIT (permissive) · bca439beb127432f · report
Attack_Linf arobey1/advbench/advbench/algorithms.py community (archive-listed) ran MIT (permissive) · 808053223b371f29 · report
AverageMeter arobey1/advbench/advbench/algorithms.py community (archive-listed) ran MIT (permissive) · 61308ee90996cb91 · report
Classifier arobey1/advbench/advbench/algorithms.py community (archive-listed) ran · fixture could not drive it MIT (permissive) · 95d7d9e951192fbe · report
MNISTNet arobey1/advbench/advbench/algorithms.py community (archive-listed) ran MIT (permissive) · cc62770b8a2f07cb · report
ResNet18 arobey1/advbench/advbench/algorithms.py community (archive-listed) ran MIT (permissive) · 35e1414137593b9e · report
TRADES_Linf arobey1/advbench/advbench/algorithms.py community (archive-listed) ran fingerprinted MIT (permissive) · 4cce9cc92ffa9b07 · report
TradesAWP val-iisc/flss/CIFAR10/Train/utils_awp.py community (archive-listed) ran no licence file found · pointer only · c1b3357620672711 · report
trades_loss TonyYaoMSU/TRADES/TRADES-master/trades.py community (archive-listed) ran · our draft was wrong no licence file found · pointer only · 4f4e01ae4a9aeecf · report
trades_loss nutellamok/advrush/advrush/trades.py community (archive-listed) ran · our draft was wrong Apache-2.0 (permissive) · ae05ac36b5660867 · report
trades_loss salomonhotegni/MOREL/src/advermorel/losses/trades.py community (archive-listed) ran · our draft was wrong MIT (permissive) · e79913f3ab121c59 · report
Algorithm arobey1/advbench/advbench/algorithms.py community (archive-listed) unverified MIT (permissive) · afdbbd69eb450e7d · report
TRADES arobey1/advbench/advbench/algorithms.py community (archive-listed) unverified MIT (permissive) · 8af50e8650fba9a4 · report
trades_loss identical code first harvested elsewhere ran · our draft was wrong licence of this copy not recorded · 0dbf499b0160d7e3 · report
TRADES_loss identical code first harvested elsewhere unverified licence of this copy not recorded · 310d3d6ec0329c05 · report

Tasks

Adversarial AttackAdversarial DefenseAdversarial RobustnessGeneral Classification

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Adversarial Attack CIFAR-10 TRADES [zhang2019b] Attack: PGD20 45.900 #3 of 6 Archive leaderboard report

Ranks are positions in the archive's leaderboards as they stood at the 2025-07-28 snapshot. Results published since then are not among these rows, so a rank here is not a current standing.

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