Papers › Regularization properties of adversarially-trained linear regression

Regularization properties of adversarially-trained linear regression

16 Oct 2023NeurIPS 2023 11arXiv:2310.10807archive 2025-07-28

Antônio H. Ribeiro, Dave Zachariah, Francis Bach, Thomas B. Schön

State-of-the-art machine learning models can be vulnerable to very small input perturbations that are adversarially constructed. Adversarial training is an effective approach to defend against it. Formulated as a min-max problem, it searches for the best solution when the training data were corrupted by the worst-case attacks. Linear models are among the simple models where vulnerabilities can be observed and are the focus of our study. In this case, adversarial training leads to a convex optimization problem which can be formulated as the minimization of a finite sum. We provide a comparative analysis between the solution of adversarial training in linear regression and other regularization methods. Our main findings are that: (A) Adversarial training yields the minimum-norm interpolating solution in the overparameterized regime (more parameters than data), as long as the maximum disturbance radius is smaller than a threshold. And, conversely, the minimum-norm interpolator is the solution to adversarial training with a given radius. (B) Adversarial training can be equivalent to parameter shrinking methods (ridge regression and Lasso). This happens in the underparametrized region, for an appropriate choice of adversarial radius and zero-mean symmetrically distributed covariates. (C) For ℓ_∞-adversarial training -- as in square-root Lasso -- the choice of adversarial radius for optimal bounds does not depend on the additive noise variance. We confirm our theoretical findings with numerical examples.

PaperPDFConference PDFCodeCode 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 1 repository linked to this paper: 8 ran (of which 0 constructed an object rather than computing a result; 8 with no instrument failure: 0 honoured, 0 violated, 8 with no contract checked; 0 where Syntology's instrument failed) · 3 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code; here there are none.

By repository: official repository: 11 samples from 1 repository, 8 ran (8 with no instrument failure; 0 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-24 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

antonior92/advtrain-linreg officialmentioned in papermentioned on GitHubMITSyntology: 11 samples, 8 ran (0 instrument-failed) · 3 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: 8 ran (of which 0 constructed an object rather than computing a result; 8 with no instrument failure: 0 honoured, 0 violated, 8 with no contract checked; 0 where Syntology's instrument failed) · 3 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.

8ran
3unverified

Licence: 0 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 antonior92/advtrain-linreg. “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.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity.

antonior92/advtrain-linreg official repository 11 samples, 8 ran (0 instrument-failed) · 3 unverified
estimate_adv_radius comparing_methods/estimate.py ran MIT (permissive) · dde87153c64c3d40 · report fixture: signature X:ndarray/2/float, _y:ndarray/1/int, seed:int/0/int, n_samples:int/0/int · returned float64 · level recorded 2026-09-24
estimate_sqrt_lasso_reg comparing_methods/estimate.py ran MIT (permissive) · 9a58fec7b7bae791 · report fixture: signature X:ndarray/2/float, _y:ndarray/1/float, seed:int/0/int, n_samples:int/0/int · returned float64 · level recorded 2026-09-24
generate_random_ortogonal datasets.py ran MIT (permissive) · 2824a1210c63d6d0 · report fixture: signature p:int/0/int, d:int/0/int, rng:RandomState/0/? · returned ndarray · level recorded 2026-09-24
get_dataset in 285 papers datasets.py ran MIT (permissive) · 6a90f732312ff406 · report fixture: returned tuple · level recorded 2026-09-24
get_median_and_quantiles magic/plot.py ran fingerprinted MIT (permissive) · 6df7e6cfbf2117d1 · report fixture: signature x:ndarray/1/int, y:ndarray/1/float · returned tuple · level recorded 2026-09-24
get_quantiles in 5 papers utils.py ran MIT (permissive) · 40ab339cc59ce96b · report fixture: signature xaxis:ndarray/1/float, r:ndarray/1/float, quantileslower:float/0/float, quantilesupper:float/0/float · returned tuple · level recorded 2026-09-24
get_quantiles_df utils.py ran MIT (permissive) · 243707ae2686e411 · report fixture: signature df:DataFrame/0/?, xname:str/0/str, yname:str/0/str · returned tuple · level recorded 2026-09-24
ridge training.py ran fingerprinted MIT (permissive) · 1a4b4921f59dd821 · report fixture: signature X:ndarray/2/float, y:ndarray/1/float, regul:float/0/float · returned ndarray · level recorded 2026-09-24
comput_advradius_zero comparing_methods/estimate.py unverified MIT (permissive) · d679e1db4f2edfe2 · report
compute_adv_attack adversarial_attack.py unverified MIT (permissive) · ec6c5f1280eb088b · report
compute_q advtrain.py unverified MIT (permissive) · b65631d31bb9f5cb · report

Tasks

regression

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Methods

FocusLinear Regression

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