Papers › Sub-Image Anomaly Detection with Deep Pyramid Correspondences

Sub-Image Anomaly Detection with Deep Pyramid Correspondences

5 May 2020arXiv:2005.02357archive 2025-07-28

Niv Cohen, Yedid Hoshen

Nearest neighbor (kNN) methods utilizing deep pre-trained features exhibit very strong anomaly detection performance when applied to entire images. A limitation of kNN methods is the lack of segmentation map describing where the anomaly lies inside the image. In this work we present a novel anomaly segmentation approach based on alignment between an anomalous image and a constant number of the similar normal images. Our method, Semantic Pyramid Anomaly Detection (SPADE) uses correspondences based on a multi-resolution feature pyramid. SPADE is shown to achieve state-of-the-art performance on unsupervised anomaly detection and localization while requiring virtually no training time.

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

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

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

any-tech/SPADE-fast mentioned on GitHubpytorchApache-2.0Syntology: 3 samples, 3 ran (0 instrument-failed) · 0 unverified report
byungjae89/SPADE-pytorch mentioned on GitHubpytorchApache-2.0Syntology: not harvested report
Burf/tfdetection tfSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Faster R-CNN: Towards Real-Time Object Detection with Region Proposal Networks (arXiv:1506.01497; that paper's own run record: 79 ran (of which 9 constructed an object rather than computing a result; 47 with no instrument failure: 18 honoured, 5 violated, 24 with no contract checked; 32 where Syntology's instrument failed) · 45 unverified), Wide Residual Networks (arXiv:1605.07146; that paper's own run record: 66 ran (of which 31 constructed an object rather than computing a result; 47 with no instrument failure: 0 honoured, 0 violated, 47 with no contract checked; 19 where Syntology's instrument failed) · 30 unverified), Encoder-Decoder with Atrous Separable Convolution for Semantic Image Segmentation (arXiv:1802.02611; that paper's own run record: 44 ran (of which 17 constructed an object rather than computing a result; 28 with no instrument failure: 2 honoured, 0 violated, 26 with no contract checked; 16 where Syntology's instrument failed) · 28 unverified) and 1 more (every one in this page's JSON twin); nothing checks that they implement this paper's method. report
areylng/SPADE-MVTEC-LOCO-AD-dataset pytorchSyntology: not harvested report
rvorias/ind_knn_ad pytorchMITSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Towards Total Recall in Industrial Anomaly Detection (arXiv:2106.08265; that paper's own run record: 28 ran (of which 0 constructed an object rather than computing a result; 25 with no instrument failure: 1 honoured, 1 violated, 23 with no contract checked; 3 where Syntology's instrument failed) · 8 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

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

3ran

Licence: 0 of the 3 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 any-tech/SPADE-fast. “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.

any-tech/SPADE-fast community (archive-listed) 3 samples, 3 ran (0 instrument-failed) · 0 unverified
calc_imagewise_metrics utils/metrics.py ran Apache-2.0 (permissive) · 81bc5452f1a7b15e · report fixture: signature D:dict/0/?, y:dict/0/? · returned tuple · level recorded 2026-09-24
calc_pixelwise_metrics utils/metrics.py ran Apache-2.0 (permissive) · a4719a76cf6728b3 · report fixture: signature D:dict/0/?, y:dict/0/? · returned tuple · level recorded 2026-09-24
overlay_heatmap_on_image utils/visualize.py ran Apache-2.0 (permissive) · 591e30226a9f25b0 · report fixture: signature img:ndarray/3/int, heatmap:ndarray/2/float, ratio_img:float/0/float · returned ndarray · level recorded 2026-09-24

Tasks

Anomaly ClassificationAnomaly DetectionAnomaly SegmentationSegmentationUnsupervised Anomaly Detection

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Anomaly Classification GoodsAD SPADE AUPR 68.7 #7 of 11 Archive leaderboard report
Anomaly Classification GoodsAD SPADE AUROC 64.1 #7 of 11 Archive leaderboard report
Anomaly Detection MVTec AD SPADE Detection AUROC 85.5 #123 of 148 Archive leaderboard report
Anomaly Detection MVTec AD SPADE FPS 1.5 #123 of 148 Archive leaderboard report
Anomaly Detection MVTec AD SPADE Segmentation AUROC 96.5 #123 of 148 Archive leaderboard report
Anomaly Detection MVTec LOCO AD SPADE Avg. Detection AUROC 68.9 #34 of 40 Archive leaderboard report
Anomaly Detection MVTec LOCO AD SPADE Detection AUROC (only logical) 70.9 #34 of 40 Archive leaderboard report
Anomaly Detection MVTec LOCO AD SPADE Detection AUROC (only structural) 66.8 #34 of 40 Archive leaderboard report
Anomaly Detection MVTec LOCO AD SPADE Segmentation AU-sPRO (until FPR 5%) 45.1 #34 of 40 Archive leaderboard report
Anomaly Detection VisA SPADE Detection AUROC 82.1 #38 of 50 Archive leaderboard report
Anomaly Detection VisA SPADE Segmentation AUPRO (until 30% FPR) 65.9 #38 of 50 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