Papers › Unleashing Mask: Explore the Intrinsic Out-of-Distribution Detection Capability

Unleashing Mask: Explore the Intrinsic Out-of-Distribution Detection Capability

6 Jun 2023arXiv:2306.03715archive 2025-07-28

Jianing Zhu, Hengzhuang Li, Jiangchao Yao, Tongliang Liu, Jianliang Xu, Bo Han

Out-of-distribution (OOD) detection is an indispensable aspect of secure AI when deploying machine learning models in real-world applications. Previous paradigms either explore better scoring functions or utilize the knowledge of outliers to equip the models with the ability of OOD detection. However, few of them pay attention to the intrinsic OOD detection capability of the given model. In this work, we generally discover the existence of an intermediate stage of a model trained on in-distribution (ID) data having higher OOD detection performance than that of its final stage across different settings, and further identify one critical data-level attribution to be learning with the atypical samples. Based on such insights, we propose a novel method, Unleashing Mask, which aims to restore the OOD discriminative capabilities of the well-trained model with ID data. Our method utilizes a mask to figure out the memorized atypical samples, and then finetune the model or prune it with the introduced mask to forget them. Extensive experiments and analysis demonstrate the effectiveness of our method. The code is available at: https://github.com/tmlr-group/Unleashing-Mask.

PaperPDFCodeCode 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 Unleashing Mask, 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='Unleashing Mask') (how to connect); the free check have('2306.03715') needs no token.

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

Code

Syntology 7 code samples harvested from 1 repository linked to this paper: 7 ran (of which 0 constructed an object rather than computing a result; 3 with no instrument failure: 1 honoured, 0 violated, 2 with no contract checked; 4 where Syntology's instrument failed) · 0 unverified. Where Syntology's instrument failed: 3 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: 7 samples from 1 repository, 7 ran (3 with no instrument failure; 4 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-26 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed. 1 of the 7 samples that ran has no recorded date.

tmlr-group/unleashing-mask officialmentioned in papermentioned on GitHubpytorchMITSyntology: 7 samples, 7 ran (4 instrument-failed) · 0 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

7 samples harvested: 7 ran (of which 0 constructed an object rather than computing a result; 3 with no instrument failure: 1 honoured, 0 violated, 2 with no contract checked; 4 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 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
3ran · our draft was wrong
1ran; the contract check could not run
2ran

Licence: 5 of the 7 samples are pointer only, meaning Syntology does not serve that copy's text. For 5 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 tmlr-group/unleashing-mask. “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. 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.

tmlr-group/unleashing-mask official repository 7 samples, 7 ran (4 instrument-failed) · 0 unverified
accumulate in 6 papers utils/net_utils.py ran MIT (permissive) · 8a42a6951b0c5e57 · report fixture: signature model:callable/0/?, f:callable/0/? · returned float · level recorded 2026-09-26
arg_to_varname in 10 papers configs/parser.py ran · our draft was wrong fingerprinted MIT (permissive) here; the stored copy is pointer only · 177a4abf40724f6e · report fixture: signature st:str/0/str · returned str · level recorded 2026-09-25
argv_to_vars in 10 papers configs/parser.py ran · our draft was wrong MIT (permissive) here; the stored copy is pointer only · ffc9d7cced6f71fb · report fixture: signature argv:list/1/str · returned list · level recorded 2026-09-25
fpr_and_fdr_at_recall in 28 papers utils/get_scores.py ran; the contract check could not run (RAISES) · metamorphic tier: invariant fingerprinted MIT (permissive) here; the stored copy is pointer only · 3853ecdb6fc74451 · report fixture: signature y_true:ndarray/1/int, y_score:ndarray/1/float, recall_level:float/0/float, pos_label:NoneType/0/? · returned float64 · level recorded 2026-09-22
get_lr in 91 papers utils/net_utils.py ran MIT (permissive) · 717f5458343a0b63 · report fixture: signature optimizer:SGD/0/? · returned float · level recorded 2026-09-26
stable_cumsum in 31 papers
census: 4 implementations from 7 papers, 3 distinct outputs across 3 buckets, one shared input per bucket this sample: bucket 2 of 3, arg 1: rank 1, kind float, dtype float32
utils/get_scores.py ran · honoured contract fingerprinted MIT (permissive) here; the stored copy is pointer only · d4acb3120a027622 · report fixture: signature arr:ndarray/1/float, rtol:float/0/float, atol:float/0/float · returned ndarray · level recorded, date not recorded
trim_preceding_hyphens in 10 papers configs/parser.py ran · our draft was wrong fingerprinted MIT (permissive) here; the stored copy is pointer only · a99f170ebd682af5 · report fixture: signature st:str/0/str · returned str · level recorded 2026-09-25

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. 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". 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.

1 assembly on this paper: 0 harvested, 1 generated.

generated Assembly for Unleashing Mask (graph method: Unleashing Mask), 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. umap_loss_gradient_step entry · level 3 · ran · honoured contract · 99d707c4d0b01d767e3a7500a1eafc647bdffdc4e07003858a3e2653289e9d67

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="2306.03715") returns these assemblies with each brick's role and wiring (how to connect).

Tasks

Out-of-Distribution Detection

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Out-of-Distribution Detection ImageNet-1k vs Curated OODs (avg.) ODIN+UMAP (ResNet-50) AUROC 89.24 #12 of 16 Archive leaderboard report
Out-of-Distribution Detection ImageNet-1k vs Curated OODs (avg.) ODIN+UMAP (ResNet-50) FPR95 40.94 #12 of 16 Archive leaderboard report
Out-of-Distribution Detection ImageNet-1k vs Places ODIN+UMAP (ResNet-50) AUROC 86.99 #15 of 25 Archive leaderboard report
Out-of-Distribution Detection ImageNet-1k vs Places ODIN+UMAP (ResNet-50) FPR95 50.06 #15 of 25 Archive leaderboard report
Out-of-Distribution Detection ImageNet-1k vs SUN ODIN+UMAP (ResNet-50) AUROC 86.92 #16 of 22 Archive leaderboard report
Out-of-Distribution Detection ImageNet-1k vs SUN ODIN+UMAP (ResNet-50) FPR95 49.69 #16 of 22 Archive leaderboard report
Out-of-Distribution Detection ImageNet-1k vs Textures ODIN+UMAP (ResNet-50) AUROC 88.35 #22 of 34 Archive leaderboard report
Out-of-Distribution Detection ImageNet-1k vs Textures ODIN+UMAP (ResNet-50) FPR95 42.02 #22 of 34 Archive leaderboard report
Out-of-Distribution Detection ImageNet-1k vs iNaturalist ODIN+UMAP (ResNet-50) AUROC 94.71 #17 of 28 Archive leaderboard report
Out-of-Distribution Detection ImageNet-1k vs iNaturalist ODIN+UMAP (ResNet-50) FPR95 21.97 #17 of 28 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