Papers › APRIL-GAN: A Zero-/Few-Shot Anomaly Classification and Segmentation Method for CVPR...
APRIL-GAN: A Zero-/Few-Shot Anomaly Classification and Segmentation Method for CVPR 2023 VAND Workshop Challenge Tracks 1&2: 1st Place on Zero-shot AD and 4th Place on Few-shot AD
Xuhai Chen, Yue Han, Jiangning Zhang
In this technical report, we briefly introduce our solution for the Zero/Few-shot Track of the Visual Anomaly and Novelty Detection (VAND) 2023 Challenge. For industrial visual inspection, building a single model that can be rapidly adapted to numerous categories without or with only a few normal reference images is a promising research direction. This is primarily because of the vast variety of the product types. For the zero-shot track, we propose a solution based on the CLIP model by adding extra linear layers. These layers are used to map the image features to the joint embedding space, so that they can compare with the text features to generate the anomaly maps. Besides, when the reference images are available, we utilize multiple memory banks to store their features and compare them with the features of the test images during the testing phase. In this challenge, our method achieved first place in the zero-shot track, especially excelling in segmentation with an impressive F1 score improvement of 0.0489 over the second-ranked participant. Furthermore, in the few-shot track, we secured the fourth position overall, with our classification F1 score of 0.8687 ranking first among all participating teams.
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):
get_harvested_code_for_paper(arxiv_id="2305.17382")get_code(code_sha256="…")with a sample'scode_sha256from the list belowget_citation_path(paper_1="2305.17382", paper_2="…")with another paper's arXiv id or titleget_concepts_for_paper(arxiv_id="2305.17382")
Code
Syntology 10 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, 1 violated, 3 with no contract checked; 2 where Syntology's instrument failed) · 4 unverified. Where Syntology's instrument failed: 2 where our contract draft was wrong; failures of Syntology's instrument, not of the code.
By repository: official repository: 10 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:
- hq-deng/AnoVL, community (archive-listed): harvested for another paper, listed under the repository
Levels written between 2026-09-22 and 2026-09-26 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed. 2 of the 6 samples that ran have no recorded date.
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
10 samples harvested: 6 ran (of which 0 constructed an object rather than computing a result; 4 with no instrument failure: 0 honoured, 1 violated, 3 with no contract checked; 2 where Syntology's instrument failed) · 4 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.
Licence: 7 of the 10 samples are pointer only, meaning Syntology does not serve that copy's text. For 7 of them, 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 bychelsea/vand-april-gan. “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.
f19962ebb134b3d7 · report
fixture: signature state_dict:dict/0/? · returned dict · level recorded, date not recorded d6cbed724d58041a · report
fixture: signature model:callable/0/?, objs:list/1/str, tokenizer:callable/0/?, device:str/0/str · returned dict · level recorded 2026-09-22 dcd422d66b0581d8 · report
fixture: signature precision:str/0/str · returned dtype · level recorded, date not recorded 4b3a4d17e1df3140 · report
fixture: signature checkpoint_path:str/0/str, map_location:str/0/str · returned dict · level recorded 2026-09-24 fb651d0a97fd4d3f · report
fixture: signature input_ids:Tensor/2/int, image_inputs:Tensor/3/float, past:NoneType/0/?, attention_mask:Tensor/2/int, position_ids:Tensor/2/int · returned dict · level recorded 2026-09-26 2a377da4a76a2d44 · report
fixture: signature cls:callable/0/? · returned type · level recorded 2026-09-26 096be08051b5c0d0 · report
ddcbd45e940484ee · report
5c7cf820e99443ff · report
f34d8f34635af394 · report
Tasks
Results from the paper archive 2025-07-28
| Task | Dataset | Model | Metric | Value | Rank at snapshot | Leaderboard | Report |
|---|---|---|---|---|---|---|---|
| Anomaly Classification | VisA | APRIL-GAN | Detection AUROC | 78.0 | #1 of 1 | Archive leaderboard | report |
| Anomaly Detection | MVTec AD | APRIL-GAN(zero-shot) | Detection AUROC | 86.1 | #120 of 148 | Archive leaderboard | report |
| Anomaly Detection | MVTec AD | APRIL-GAN(zero-shot) | Segmentation AP | 40.8 | #120 of 148 | Archive leaderboard | report |
| Anomaly Detection | MVTec AD | APRIL-GAN(zero-shot) | Segmentation AUPRO | 44.0 | #120 of 148 | Archive leaderboard | report |
| Anomaly Detection | MVTec AD | APRIL-GAN(zero-shot) | Segmentation AUROC | 87.6 | #120 of 148 | Archive leaderboard | report |
| Anomaly Detection | VisA | APRIL-GAN | Detection AUROC | 78.0 | #42 of 50 | Archive leaderboard | report |
| Anomaly Detection | VisA | APRIL-GAN | F1-Score | 32.3 | #42 of 50 | Archive leaderboard | report |
| Anomaly Detection | VisA | APRIL-GAN | Segmentation AUPRO | 86.8 | #42 of 50 | Archive leaderboard | report |
| Anomaly Detection | VisA | APRIL-GAN | Segmentation AUROC | 94.2 | #42 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.
Methods
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