Papers › Robustness May Be at Odds with Accuracy

Robustness May Be at Odds with Accuracy

30 May 2018ICLR 2019 5arXiv:1805.12152archive 2025-07-28

Dimitris Tsipras, Shibani Santurkar, Logan Engstrom, Alexander Turner, Aleksander Madry

We show that there may exist an inherent tension between the goal of adversarial robustness and that of standard generalization. Specifically, training robust models may not only be more resource-consuming, but also lead to a reduction of standard accuracy. We demonstrate that this trade-off between the standard accuracy of a model and its robustness to adversarial perturbations provably exists in a fairly simple and natural setting. These findings also corroborate a similar phenomenon observed empirically in more complex settings. Further, we argue that this phenomenon is a consequence of robust classifiers learning fundamentally different feature representations than standard classifiers. These differences, in particular, seem to result in unexpected benefits: the representations learned by robust models tend to align better with salient data characteristics and human perception.

PaperPDFConference PDFCode

In Syntology View this paper on Syntology, its page in Syntology's graph. That page 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

AugustineCha/pytorch-adversarial-training-master mentioned on GitHubpytorchSyntology: not harvested report
MadryLab/robust-features-code mentioned on GitHubtfSyntology: not harvested report
XgDuan/pytorch-adversarial-training-nonexpansive mentioned on GitHubpytorchSyntology: not harvested report
conference-submission-anon/LAT_adversarial_robustness mentioned on GitHubtfSyntology: not harvested report
louis2889184/adversarial_training mentioned on GitHubpytorchSyntology: not harvested report
louis2889184/pytorch-adversarial-training mentioned on GitHubpytorchSyntology: not harvested report
msingh27/LAT_adversarial_robustness mentioned on GitHubtfSyntology: not harvested report
salomonhotegni/MOREL pytorchSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Theoretically Principled Trade-off between Robustness and Accuracy (arXiv:1901.08573; that paper's own run record: 12 ran (of which 6 constructed an object rather than computing a result; 7 with no instrument failure: 0 honoured, 0 violated, 7 with no contract checked; 5 where Syntology's instrument failed) · 3 unverified); nothing checks that they implement this paper's method. 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.

A paper named beside a repository with no sample linked to this paper is shown with that paper's own run record, not this paper's: “ran” means executed on a synthesized input, not that the code is correct, and “where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Papers are listed in arXiv-id order, at most three per repository.

Code Syntology ran Syntology

Not run by Syntology. Nothing on this page verifies that the listed code works.

Tasks

Adversarial Robustness

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