Papers › Classification-Based Anomaly Detection for General Data

Classification-Based Anomaly Detection for General Data

5 May 2020ICLR 2020 1arXiv:2005.02359archive 2025-07-28

Liron Bergman, Yedid Hoshen

Anomaly detection, finding patterns that substantially deviate from those seen previously, is one of the fundamental problems of artificial intelligence. Recently, classification-based methods were shown to achieve superior results on this task. In this work, we present a unifying view and propose an open-set method, GOAD, to relax current generalization assumptions. Furthermore, we extend the applicability of transformation-based methods to non-image data using random affine transformations. Our method is shown to obtain state-of-the-art accuracy and is applicable to broad data types. The strong performance of our method is extensively validated on multiple datasets from different domains.

PaperPDFConference PDFCodeCode Syntology ranMethod as code

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.

Syntology holds a reference implementation of GOAD, generated from the paper text (not the authors' code), at level 3 on Syntology's ladder: V2 “two implementations GENERATED from the paper's signature and spec agree numerically (1e-6) on fixture inputs” “neither of the two ever read the authors' own code, so V2 measures how unambiguously the paper specifies the method, not fidelity to the authors' implementation (measured 2026-09-11, commit 75eaa77: cross_checked_by is a second LLM on 2,628 of 2,831 served samples)”; V3 “paper-derived property tests pass on both of those same two generations.” (quoted from Syntology's server card). No rung compares this code against the authors' implementation. For agents: get_reference_implementation(name='GOAD') (how to connect); the free check have('2005.02359') needs no token.

For agents, on Syntology's MCP service (how to connect):

Code

Syntology 10 code samples harvested from 2 repositories linked to this paper: 5 ran (of which 3 constructed an object rather than computing a result; 5 with no instrument failure: 0 honoured, 0 violated, 5 with no contract checked; 0 where Syntology's instrument failed) · 5 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code; here there are none.

By repository: community (archive-listed): 10 samples from 2 repositories, 5 ran (5 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 between 2026-09-22 and 2026-09-24 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

lironber/GOAD pytorchSyntology: 4 samples, 3 ran (0 instrument-failed) · 1 unverified report
xuhongzuo/DeepOD pytorchSyntology: 6 samples, 2 ran (0 instrument-failed) · 4 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

10 samples harvested: 5 ran (of which 3 constructed an object rather than computing a result; 5 with no instrument failure: 0 honoured, 0 violated, 5 with no contract checked; 0 where Syntology's instrument failed) · 5 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.

5ran
5unverified

Licence: 4 of the 10 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 2 repositories linked to this paper, official or community; the list below is grouped by repository, each group headed by its name and what it is to the paper. “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”. For 1 sample that ran, the graph records a signature this page does not show: for a class the fixture built without calling, the harness called the object with inputs it made up itself, so the recorded signature is the harness's probe, not the fixture's arguments. “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. A census tag appears when Syntology's census ran implementations with that name on one shared input per bucket: it gives how many were compared, from how many papers, and how many distinct outputs they produced, and names this sample's bucket when this sample was one of them.

lironber/GOAD community (archive-listed) 4 samples, 3 ran (0 instrument-failed) · 1 unverified
BasicBlock in 126 papers
census: 6 implementations from 6 papers, 5 distinct outputs on one shared input
opt_tc.py ran · metamorphic tier: deterministic fingerprinted licence not identified · pointer only · cf4931227198dd5e · report fixture: returned BasicBlock · level recorded 2026-09-22
TransClassifier opt_tc.py ran licence not identified · pointer only · ce56fb1d9e246c60 · report fixture: returned TransClassifier · level recorded 2026-09-22
WideResNet in 13 papers opt_tc.py ran · metamorphic tier: deterministic licence not identified · pointer only · e078996c88b6841f · report fixture: returned WideResNet · level recorded 2026-09-22
tc_loss opt_tc.py unverified licence not identified · pointer only · 145b6369ec05d217 · report
xuhongzuo/DeepOD community (archive-listed) 6 samples, 2 ran (0 instrument-failed) · 4 unverified
ConvNet in 13 papers deepod/models/tabular/goad.py ran fingerprinted BSD-2-Clause (permissive) · 51a1f05a69ec1e74 · report fixture: signature x:Tensor/3/float · returned Tensor · level recorded 2026-09-24
GoadNet deepod/models/tabular/goad.py ran · metamorphic tier: deterministic fingerprinted BSD-2-Clause (permissive) · 4b1b91ea3ab31366 · report fixture: signature x:Tensor/3/float · returned tuple · level recorded 2026-09-22
BaseDeepAD deepod/models/tabular/goad.py unverified BSD-2-Clause (permissive) · 50858634cfdf1e31 · report
GOAD deepod/models/tabular/goad.py unverified BSD-2-Clause (permissive) · a3682ac4cb5c81da · report
GoadLoss deepod/models/tabular/goad.py unverified BSD-2-Clause (permissive) · 6e0c09bc42f6e2c2 · report
weights_init in 44 papers deepod/models/tabular/goad.py unverified BSD-2-Clause (permissive) · 058e8db0c4bedef9 · report

Method as code Syntology

What Syntology's graph records as this paper's claimed method, lifted into code: each assembly names its bricks (functions and classes), each with its own role and its own verification level. An assembly is not a check that the code implements the method correctly or reproduces the paper's results. Levels are each brick's own verification level in Syntology's graph (level 0: no recorded run), listed brick by brick and never combined into one level; “ran” means the brick executed on a synthesized input, not that its output is correct, and the instrument figure counts failures of Syntology's instrument, not of the code. For a generated assembly, an independent peer is a second implementation generated separately from the same paper text; neither implementation read the authors' code. At level 2 the two agreed numerically on the fixture's inputs; level 3 is recorded when property tests derived from the paper also passed on both, and each level 3 card prints how many its report lists. Where a model read the code against the paper's claim, each assembly's label verdict is one model's judgement, kept in this page's JSON twin; it is not calibrated, so no card prints it. A generated assembly's label was set when its code was generated for the method, and no model judged it; its card prints it as "by construction" or "not judged by a model". Siblings are assemblies lifted from this paper in the same batch for the same method: alternative readings kept side by side; none replaces or supersedes another. Where an assembly's phrase has no constructed figure, a brick that ran is not among the harvested samples this build reads, and whether a brick's run only constructed an object is read from that brick's harvested sample, so the figure was not counted; it does not say there were none.

3 assemblies on this paper: 2 harvested, 1 generated, listed in 2 groups (siblings lifted in one batch form one group).

generated Assembly for GOAD (graph method: GOAD), generated from the paper text, not the repository's code. 1 brick; individually on a fixture: 1 ran (1 with no instrument failure: 1 honoured, 0 violated, 0 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified. Ran end-to-end against an independent peer (level 3; 5 property tests passed on both).

label matches by construction: the code was generated for this method (not judged by a model)

  1. goad_anomaly_score entry · level 3 · ran · honoured contract · a93a23d153ef951c306f4a1e768794d8e13347ce46df8900338083458de67b07

2 sibling assemblies for GOAD (harvested), lifted in the same batch on 2026-09-09: alternative readings kept side by side; none replaces or supersedes another.

harvested Assembly for GOAD (graph method: GOAD). 5 bricks; individually on a fixture: 4 ran (of which 4 constructed an object rather than computing a result; 4 with no instrument failure: 0 honoured, 0 violated, 4 with no contract checked; 0 where Syntology's instrument failed) · 1 unverified; every one of the 4 samples that ran constructed an object rather than computing a result. The assembly has not been run end-to-end.

one of 2 siblings

  1. TransClassifier entry · level 1 · ran · ce56fb1d9e246c60
  2. WideResNet model · level 1 · ran · e078996c88b6841f
  3. tc_loss loss · level 0 · unverified · 145b6369ec05d217
  4. BasicBlock helper · level 1 · ran · cf4931227198dd5e
  5. NetworkBlock helper · level 1 · ran · db462e0cc17e19f9

harvested Assembly for GOAD (graph method: GOAD). 9 bricks; individually on a fixture: 5 ran (of which 0 constructed an object rather than computing a result; 2 with no instrument failure: 0 honoured, 0 violated, 2 with no contract checked; 3 where Syntology's instrument failed) · 4 unverified. The assembly has not been run end-to-end.

one of 2 siblings

  1. GOAD entry · level 0 · unverified · a3682ac4cb5c81da
  2. BaseDeepAD helper · level 0 · unverified · 50858634cfdf1e31
  3. GoadLoss loss · level 0 · unverified · 6e0c09bc42f6e2c2
  4. GoadNet model · level 1 · ran · 4b1b91ea3ab31366
  5. weights_init helper · level 0 · unverified · 058e8db0c4bedef9
  6. get_sub_seqs helper · level 1 · ran; the contract check could not run · a1a5760d9effd68a
  7. get_sub_seqs_label helper · level 1 · ran; the contract check could not run · 5fd7000332dae116
  8. ConvNet helper · level 1 · ran · 51a1f05a69ec1e74
  9. _instantiate_class helper · level 1 · ran · our draft was wrong · a2bfe81fe3467af3

Each brick ends with its code_sha256, Syntology's identity for that exact code; click one to copy the get_code call that returns it. For agents, on Syntology's MCP service: assembly(arxiv_id="2005.02359") returns these assemblies with each brick's role and wiring (how to connect).

Tasks

Anomaly DetectionClassificationGeneral Classification

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Anomaly Detection Anomaly Detection on Anomaly Detection on Unlabeled ImageNet-30 vs Flowers-102 GOAD Network ResNet-18 #4 of 5 Archive leaderboard report
Anomaly Detection Anomaly Detection on Anomaly Detection on Unlabeled ImageNet-30 vs Flowers-102 GOAD ROC-AUC 92.8 #4 of 5 Archive leaderboard report
Anomaly Detection Anomaly Detection on Unlabeled CIFAR-10 vs LSUN (Fix) GOAD Network ResNet-18 #8 of 8 Archive leaderboard report
Anomaly Detection Anomaly Detection on Unlabeled CIFAR-10 vs LSUN (Fix) GOAD ROC-AUC 78.8 #8 of 8 Archive leaderboard report
Anomaly Detection Anomaly Detection on Unlabeled ImageNet-30 vs CUB-200 GOAD Network ResNet-18 #3 of 5 Archive leaderboard report
Anomaly Detection Anomaly Detection on Unlabeled ImageNet-30 vs CUB-200 GOAD ROC-AUC 90.5 #3 of 5 Archive leaderboard report
Anomaly Detection One-class CIFAR-10 GOAD AUROC 88.2 #22 of 36 Archive leaderboard report
Anomaly Detection UEA time-series datasets GOAD Avg. ROC-AUC 87.2 #2 of 3 Archive leaderboard report
Anomaly Detection Unlabeled CIFAR-10 vs CIFAR-100 GOAD AUROC 89.2 #8 of 13 Archive leaderboard report
Anomaly Detection Unlabeled CIFAR-10 vs CIFAR-100 GOAD Network ResNet-18 #8 of 13 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