Papers › A Unified Anomaly Synthesis Strategy with Gradient Ascent for Industrial Anomaly...

A Unified Anomaly Synthesis Strategy with Gradient Ascent for Industrial Anomaly Detection and Localization

12 Jul 2024arXiv:2407.09359archive 2025-07-28

Qiyu Chen, Huiyuan Luo, Chengkan Lv, Zhengtao Zhang

Anomaly synthesis strategies can effectively enhance unsupervised anomaly detection. However, existing strategies have limitations in the coverage and controllability of anomaly synthesis, particularly for weak defects that are very similar to normal regions. In this paper, we propose Global and Local Anomaly co-Synthesis Strategy (GLASS), a novel unified framework designed to synthesize a broader coverage of anomalies under the manifold and hypersphere distribution constraints of Global Anomaly Synthesis (GAS) at the feature level and Local Anomaly Synthesis (LAS) at the image level. Our method synthesizes near-in-distribution anomalies in a controllable way using Gaussian noise guided by gradient ascent and truncated projection. GLASS achieves state-of-the-art results on the MVTec AD (detection AUROC of 99.9%), VisA, and MPDD datasets and excels in weak defect detection. The effectiveness and efficiency have been further validated in industrial applications for woven fabric defect detection. The code and dataset are available at: https://github.com/cqylunlun/GLASS.

PaperPDFCodeCode 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 8 code samples harvested from 1 repository linked to this paper: 6 ran (of which 0 constructed an object rather than computing a result; 4 with no instrument failure: 0 honoured, 0 violated, 4 with no contract checked; 2 where Syntology's instrument failed) · 2 unverified. Where Syntology's instrument failed: 1 where our contract draft was wrong; 1 where the contract check could not run; failures of Syntology's instrument, not of the code.

By repository: official repository: 8 samples from 1 repository, 6 ran (4 with no instrument failure; 2 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.

No sample is linked to this paper from 1 of its repositories that Syntology harvested for other papers:

Levels written between 2026-09-24 and 2026-09-25 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

cqylunlun/glass officialmentioned in papermentioned on GitHubpytorchMITSyntology: 8 samples, 6 ran (2 instrument-failed) · 2 unverified report
septmars/DL pytorchMITSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Exploring Intrinsic Normal Prototypes within a Single Image for Universal Anomaly Detection (arXiv:2503.02424; that paper's own run record: 4 ran (of which 1 constructed an object rather than computing a result; 1 with no instrument failure: 0 honoured, 0 violated, 1 with no contract checked; 3 where Syntology's instrument failed) · 1 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

8 samples harvested: 6 ran (of which 0 constructed an object rather than computing a result; 4 with no instrument failure: 0 honoured, 0 violated, 4 with no contract checked; 2 where Syntology's instrument failed) · 2 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

1ran · our draft was wrong
1ran; the contract check could not run
4ran
2unverified

Licence: 1 of the 8 samples is pointer only, meaning Syntology does not serve that copy's text. For that sample, this paper's copy is under a permissive licence and cleared, but the stored copy of the same code that Syntology serves is not; the licence label's tooltip gives Syntology's recorded reason. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from cqylunlun/glass. “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.

cqylunlun/glass official repository 8 samples, 6 ran (2 instrument-failed) · 2 unverified
compute_best_pr_re metrics.py ran; the contract check could not run (RAISES) fingerprinted MIT (permissive) · 445abda186be8f3e · report fixture: signature anomaly_ground_truth_labels:ndarray/1/int, anomaly_prediction_weights:ndarray/1/float · returned tuple · level recorded 2026-09-24
compute_imagewise_retrieval_metrics metrics.py ran MIT (permissive) · 0ed340136461ba43 · report fixture: signature anomaly_prediction_weights:ndarray/1/float, anomaly_ground_truth_labels:ndarray/1/int, path:str/0/str · returned dict · level recorded 2026-09-24
compute_pixelwise_retrieval_metrics metrics.py ran MIT (permissive) · b10a57e7570128c5 · report fixture: signature anomaly_segmentations:list/1/ndarray, ground_truth_masks:list/1/ndarray, path:str/0/str · returned dict · level recorded 2026-09-24
create_storage_folder utils.py ran MIT (permissive) · bd60fc834523d1a1 · report fixture: signature main_folder_path:str/0/str, project_folder:str/0/str, group_folder:str/0/str, run_name:str/0/str, mode:str/0/str · returned str · level recorded 2026-09-24
lerp_np in 9 papers perlin.py ran MIT (permissive) here; the stored copy is pointer only · 4de91a4627a51ea2 · report fixture: signature x:ndarray/2/float, y:ndarray/2/float, w:ndarray/2/float · returned ndarray · level recorded 2026-09-25
set_torch_device utils.py ran · our draft was wrong MIT (permissive) · 61fd3c8459a48853 · report fixture: signature gpu_ids:list/1/empty · returned device · level recorded 2026-09-24
distribution_judge utils.py unverified MIT (permissive) · e7806e6d1dca9761 · report
load in 392 papers backbones.py unverified MIT (permissive) · c07c74fd129adbcc · report

Tasks

Anomaly DetectionDefect DetectionUnsupervised Anomaly Detection

Datasets

Introduced by this paper, per the archive.

WFDD

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Anomaly Detection MPDD GLASS Detection AUROC 99.6 #1 of 16 Archive leaderboard report
Anomaly Detection MPDD GLASS Segmentation AUPRO 98.2 #1 of 16 Archive leaderboard report
Anomaly Detection MPDD GLASS Segmentation AUROC 99.4 #1 of 16 Archive leaderboard report
Anomaly Detection MVTec AD GLASS Detection AUROC 99.9 #1 of 148 Archive leaderboard report
Anomaly Detection MVTec AD GLASS Segmentation AUPRO 96.8 #1 of 148 Archive leaderboard report
Anomaly Detection MVTec AD GLASS Segmentation AUROC 99.3 #1 of 148 Archive leaderboard report
Anomaly Detection VisA GLASS Detection AUROC 98.8 #8 of 50 Archive leaderboard report
Anomaly Detection VisA GLASS Segmentation AUPRO (until 30% FPR) 92.8 #8 of 50 Archive leaderboard report
Anomaly Detection VisA GLASS Segmentation AUROC 98.8 #8 of 50 Archive leaderboard report
Anomaly Detection WFDD GLASS Detection AUROC 100 #1 of 1 Archive leaderboard report
Anomaly Detection WFDD GLASS Segmentation AUPRO 94.9 #1 of 1 Archive leaderboard report
Anomaly Detection WFDD GLASS Segmentation AUROC 98.9 #1 of 1 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