Methods › General › Adversarial Training › Accuracy-Robustness Area (ARA)

Accuracy-Robustness Area

Accuracy-Robustness Area (ARA)

3 papers tagged archive 2025-07-28

Introduced by Walt Woods et al. in Adversarial Explanations for Understanding Image Classification Decisions and Improved Neural Network Robustness

archive 2025-07-28 Description, source and code snippet are the archive's method entry.

In the space of adversarial perturbation against classifier accuracy, the ARA is the area between a classifier's curve and the straight line defined by a naive classifier's maximum accuracy. Intuitively, the ARA measures a combination of the classifier’s predictive power and its ability to overcome an adversary. Importantly, when contrasted against existing robustness metrics, the ARA takes into account the classifier’s performance against all adversarial examples, without bounding them by some arbitrary ϵ.

PaperSource

In Syntology name not resolved (unknown_name). The lookup matched no method, paper or venue by this name; that asserts nothing about whether code exists.

Near matches the lookup lists, each a different name: Parametric Robustness Sets; accuracy-stability-robustness loss; Angle Robustness Navigation Paradigm; Area Under the Rank Accuracy Curve (AURAC); metric for trade-off between clean accuracy and adversarial robustness; LARAR (Layer-wise Adversarial Robustness using Adaptive Regularization).

Syntology's have check for this name (free, it answers coverage only), read 2026-10-05; ask it again live. A level is the served verification level of that one answer; nothing here is summed across methods.

Papers archive 2025-07-28

archive papers tagged: 3 · with a code link: 3 · where Syntology ran a sample: 0 (0 with a run with no instrument failure, 0 where every run was a failure of Syntology's instrument) Syntology

Show: all tagged papersonly where code ran: none of the 3 tagged papers has a Syntology run on record

Page 1 of 1: papers 1 to 3 of 3, newest first by the archive's date (ties by slug), in archive order.

Repository counts are the archive's code-links table. A Syntology line states what Syntology ran from that paper's harvested code, as “N ran (of which C constructed an object rather than computing a result; K with no instrument failure: H honoured, V violated, P with no contract checked; I where Syntology's instrument failed) · U unverified”; the instrument figure counts failures of Syntology's instrument, not of the code. It is per sample and not a correctness claim. When the archive marks a repository official for the paper, the line starts with that repository's state (the archive's flag, not a verdict on who wrote the code; “community repositories only” when every sample that ran came from a community repository, “official: no sample here; runs from other or unrecorded repositories” when some came from a repository the paper names or has in its text, or from none recorded); hover it for the repositories the samples that ran came from.

Tasks archive 2025-07-28

9 tasks the archive attaches to papers tagged with this method, by distinct papers. A task without a page in the catalog is plain text.

TaskPapers
Adversarial Defense1
Fact Checking1
Fake News Detection1
Fraud Detection1
General Classification1
Image Classification1
Interpretable Machine Learning1
Robust classification1
image-classification1

Usage over time archive 2025-07-28

Papers per year tagged with Accuracy-Robustness Area (ARA): 2019 to 2024, peak 2 2 0 2019: 2 papers 2019 2020: 0 papers 2020 2021: 0 papers 2021 2022: 0 papers 2022 2023: 0 papers 2023 2024: 1 paper 2024
Papers per year the archive tags with this method, by the paper's archive date (3 dated). Bars are counts, not a trend claim.

Components: the archive holds no method-to-method composition, so PwC's Components table cannot be rebuilt; the Papers list carries no Results column for the same reason (the archive does not join its leaderboard rows to method tags).

Categories archive 2025-07-28

Adversarial Training

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