Papers › ResAD: A Simple Framework for Class Generalizable Anomaly Detection

ResAD: A Simple Framework for Class Generalizable Anomaly Detection

26 Oct 2024arXiv:2410.20047archive 2025-07-28

Xincheng Yao, Zixin Chen, Chao GAO, Guangtao Zhai, Chongyang Zhang

This paper explores the problem of class-generalizable anomaly detection, where the objective is to train one unified AD model that can generalize to detect anomalies in diverse classes from different domains without any retraining or fine-tuning on the target data. Because normal feature representations vary significantly across classes, this will cause the widely studied one-for-one AD models to be poorly classgeneralizable (i.e., performance drops dramatically when used for new classes). In this work, we propose a simple but effective framework (called ResAD) that can be directly applied to detect anomalies in new classes. Our main insight is to learn the residual feature distribution rather than the initial feature distribution. In this way, we can significantly reduce feature variations. Even in new classes, the distribution of normal residual features would not remarkably shift from the learned distribution. Therefore, the learned model can be directly adapted to new classes. ResAD consists of three components: (1) a Feature Converter that converts initial features into residual features; (2) a simple and shallow Feature Constraintor that constrains normal residual features into a spatial hypersphere for further reducing feature variations and maintaining consistency in feature scales among different classes; (3) a Feature Distribution Estimator that estimates the normal residual feature distribution, anomalies can be recognized as out-of-distribution. Despite the simplicity, ResAD can achieve remarkable anomaly detection results when directly used in new classes. The code is available at https://github.com/xcyao00/ResAD.

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 11 code samples harvested from 1 repository linked to this paper: 9 ran (of which 0 constructed an object rather than computing a result; 7 with no instrument failure: 1 honoured, 0 violated, 6 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: 11 samples from 1 repository, 9 ran (7 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.

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

xcyao00/resad officialmentioned in papermentioned on GitHubpytorchMITSyntology: 11 samples, 9 ran (2 instrument-failed) · 2 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: 9 ran (of which 0 constructed an object rather than computing a result; 7 with no instrument failure: 1 honoured, 0 violated, 6 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 · honoured contract
1ran · our draft was wrong
1ran; the contract check could not run
6ran
2unverified

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 xcyao00/resad. “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.

xcyao00/resad official repository 11 samples, 9 ran (2 instrument-failed) · 2 unverified
get_logp_a losses/utils.py ran MIT (permissive) · 4864e6c6c42523f8 · report fixture: signature C:int/0/int, z:Tensor/2/float, logdet_J:Tensor/1/float · returned Tensor · level recorded 2026-09-25
get_logp_boundary losses/loss.py ran MIT (permissive) · 6871690b7d7c52ca · report fixture: signature logps:Tensor/1/float, mask:Tensor/1/float, pos_beta:float/0/float, margin_tau:float/0/float, normalizer:int/0/int · returned tuple · level recorded 2026-09-25
get_normal_boundary losses/utils.py ran MIT (permissive) · 97bb30729343aee3 · report fixture: signature logps:Tensor/1/float, mask:Tensor/1/int, pos_beta:float/0/float · returned Tensor · level recorded 2026-09-25
get_position_encoding models/modules.py ran fingerprinted MIT (permissive) · 5461edac0e02cae6 · report fixture: signature D:int/0/int, H:int/0/int, W:int/0/int · returned Tensor · level recorded 2026-09-25
load_and_transform_vision_data in 9 papers main_ib.py ran · honoured contract MIT (permissive) · 5697b41685ddd400 · report fixture: signature image_paths:list/1/str, device:device/0/? · returned Tensor · level recorded 2026-09-25
load_mc_reference_features main_all.py ran MIT (permissive) · 8724d875b88a147c · report fixture: signature root_dir:str/0/str, class_names:list/1/str, device:device/0/?, num_shot:int/0/int · returned dict · level recorded 2026-09-25
load_mc_reference_features main_ib.py ran MIT (permissive) · 38f73e38d215dec7 · report fixture: signature root_dir:str/0/str, class_names:list/1/str, device:device/0/?, num_shot:int/0/int · returned dict · level recorded 2026-09-25
load_reference_features cpr.py ran; the contract check could not run (RAISES) MIT (permissive) · 247b256eed3c80d3 · report fixture: signature class_name:str/0/str · returned Tensor · level recorded 2026-09-25
subnet_fc in 8 papers models/fc_flow.py ran · our draft was wrong MIT (permissive) · 3f068df64f534372 · report fixture: signature dims_in:int/0/int, dims_out:int/0/int · returned Sequential · level recorded 2026-09-25
calculate_log_barrier_occ_loss losses/loss.py unverified MIT (permissive) · 09544c0c0a013039 · report
calculate_occ_loss losses/loss.py unverified MIT (permissive) · 5ac595999ee650c5 · report

Tasks

Anomaly Detection

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

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