From Benchmark Performance to Tool Deployment: Human-in-the-Loop Anomaly Detection

arXiv cs.LG Papers

Summary

This paper evaluates 19 unsupervised anomaly detection models on the BowTie manufacturing dataset, finding performance less stable than benchmarks suggest, and presents a deployed human-in-the-loop framework for manufactured-part inspection.

arXiv:2608.07770v1 Announce Type: new Abstract: Automated anomaly detection methods often report strong performance on curated academic benchmarks, but their behavior under real-world industrial conditions is less clear. In this work, we evaluate 19 unsupervised anomaly detection models on the BowTie dataset, a challenging manufacturing dataset with reflective surfaces, subtle defects, and profile-specific variation. In contrast to benchmark results, we observe that model performance is less stable than typically reported on standard benchmarks such as MVTec AD, highly sensitive to preprocessing, and inconsistent across conditions, with no single approach emerging as uniformly robust; a consensus audit further indicates that nominal-data quality affects deployment. Motivated by these findings, we developed and initially deployed a unified human-in-the-loop framework for manufactured-part inspection that combines image annotation, AI-assisted defect detection, and an integrated validation engine, replacing a prior manual visual inspection and documentation workflow. The system supports heatmap-guided defect review, SAM-refined candidate regions for inspector acceptance, rejection, or boundary adjustment, mask evaluation where annotations exist, and review history for inspector consistency and onboarding. Together, the results highlight the gap between benchmark performance and deployment reality, and provide a practical framework for addressing it.
Original Article
View Cached Full Text

Cached at: 08/11/26, 08:06 AM

# From Benchmark Performance to Tool Deployment: Human-in-the-Loop Anomaly Detection
Source: [https://arxiv.org/html/2608.07770](https://arxiv.org/html/2608.07770)
Mike Szklarzewski1, CJ George1, Gavin Smithson1, Christopher Stokes1, Dakota Fulp1, William M\. Jones14 Benjamin Wynn2, Alexander Ur3, Agit Yesiloz5, Clint Kallenbach6 Mark Swartz6, Nathan DeBardeleben4, Sharmistha Chakrabarti4

###### Abstract

Automated anomaly detection methods often report strong performance on curated academic benchmarks, but their behavior under real\-world industrial conditions is less clear\. In this work, we evaluate 19 unsupervised anomaly detection models on the BowTie dataset, a challenging manufacturing dataset with reflective surfaces, subtle defects, and profile\-specific variation\. In contrast to benchmark results, we observe that model performance is less stable than typically reported on standard benchmarks such as MVTec AD, highly sensitive to preprocessing, and inconsistent across conditions, with no single approach emerging as uniformly robust; a consensus audit further indicates that nominal\-data quality affects deployment\.

Motivated by these findings, we developed and initially deployed a unified human\-in\-the\-loop framework for manufactured\-part inspection that combines image annotation, AI\-assisted defect detection, and an integrated validation engine, replacing a prior manual visual inspection and documentation workflow\. The system supports heatmap\-guided defect review, SAM\-refined candidate regions for inspector acceptance, rejection, or boundary adjustment, mask evaluation where annotations exist, and review history for inspector consistency and onboarding\. Together, the results highlight the gap between benchmark performance and deployment reality, and provide a practical framework for addressing it\.

††footnotetext:*Corresponding author: Sharmistha Chakrabarti*\([schakrabarti@lanl\.gov](https://arxiv.org/html/2608.07770v1/mailto:[email protected])\)\. This manuscript has been approved for unlimited release and has been assigned LA\-UR\-26\-23692\. This work has been authored by an employee of Triad National Security, LLC which operates Los Alamos National Laboratory under Contract No\. 89233218CNA000001 with the U\.S\. Department of Energy/National Nuclear Security Administration\. The publisher, by accepting the article for publication, acknowledges that the United States Government retains a non\-exclusive, paid\-up, irrevocable, world\-wide license to publish or reproduce the published form of the manuscript, or allow others to do so, for United States Government purposes\.## IIntroduction

Modern manufacturing and quality control systems continue to grow in scale and complexity, placing increasing demands on performance, efficiency, and reliability\. Within national laboratory environments such as Los Alamos National Laboratory \(LANL\), these challenges are further amplified by the need to design, fabricate, and evaluate highly specialized, often one\-off or low\-volume components that directly support the national security mission\. Unlike traditional high\-volume manufacturing, these workflows frequently involve custom geometries, evolving design requirements, and strict engineering tolerances, where even subtle defects can have significant downstream implications\.

These challenges are particularly evident in scenarios where defects are rare, subtle, or highly variable in morphology, such as in precision manufacturing and experimental system evaluation\. In these environments \(theBowTiedataset\[[18](https://arxiv.org/html/2608.07770#bib.bib1)\]is one such example\), identifying the mere presence of an anomaly is insufficient; researchers and inspectors must precisely localize and quantify the spatial extent of the defect to ensure structural integrity and compliance with strict engineering tolerances\.

However, deploying anomaly detection models in a practical, operational workflow reveals systemic bottlenecks\. Many existing solutions are tightly coupled to command\-line interfaces or “black box” inference engines\. This creates a persistent operational disconnect between thedata annotationprocess \(curating ground\-truth\), themodel inferencestage \(generating and visualizing predictions\), andstatistical validation\(quantifying model success\)\. In the motivating manual visual inspection and documentation workflow, inspectors manually reviewed each part image in a standalone viewer and logged defect observations and accept/reject decisions in a spreadsheet\. That process relied almost entirely on individual visual judgment, without preserving localized defect rationale or supporting consistent comparison across inspectors\. Our goal was therefore twofold: to make inspection easier and more consistent by combining image viewing, defect annotation, and ML\-assisted anomaly localization in one environment while keeping final disposition under inspector control, and to create a continuous improvement cycle in which finalized inspections become structured data for retraining and redeploying models over time\. This tighter integration also improves downstream communication, reproducibility, and quantitative evaluation, while preserving review history for inspector onboarding and consistency checks against expert\-reviewed cases\.

This paper contributes a 19\-model BowTie benchmark under profile and preprocessing variation, a consensus audit of nominal\-data quality, and a unified, extensible software framework comprisingAnnoMatefor guided image annotation and review,MicroSentryAIfor AI\-assisted defect localization and segmentation review, and a dedicatedValidation Enginefor mask\-based evaluation and comparison against expert reference annotations where ground truth is available\[[17](https://arxiv.org/html/2608.07770#bib.bib2)\]\. The same reference\-based comparison also supports inspector onboarding by allowing trainee decisions and annotations to be compared against expert\-reviewed cases\. The framework keeps the modules decoupled but interoperable; Section[VI](https://arxiv.org/html/2608.07770#S6)gives the architecture and workflow details\. To keep that motivation concrete, the paper first establishes the BowTie study design \(Section[III](https://arxiv.org/html/2608.07770#S3)\), empirical findings \(Sections[IV](https://arxiv.org/html/2608.07770#S4)–[V](https://arxiv.org/html/2608.07770#S5)\), and then returns to the unified framework that operationalizes those lessons in practice \(Section[VI](https://arxiv.org/html/2608.07770#S6)\)\.

## IIRelated Work

Most prior work in industrial anomaly detection \(IAD\) has focused on model accuracy, sensing pipelines, and automated monitoring rather than on inspector\-centered annotation workflows\. Reviews of anomaly detection in additive manufacturing and practical inspection systems for metallic parts or laser directed energy deposition emphasize process monitoring, defect localization, and deployment\-oriented sensing\[[27](https://arxiv.org/html/2608.07770#bib.bib3),[5](https://arxiv.org/html/2608.07770#bib.bib4),[14](https://arxiv.org/html/2608.07770#bib.bib5)\]\. At the annotation level, spatial ground truth is often created with general\-purpose tools such as VIA and LabelMe\[[11](https://arxiv.org/html/2608.07770#bib.bib6),[26](https://arxiv.org/html/2608.07770#bib.bib7)\]\. These tools are effective polygon editors, but they are not tightly coupled to anomaly\-model inference, interactive threshold tuning, contour simplification, synchronized heatmap visualization, or reciprocal comparison between human annotations and model outputs\. AnnoMate is intended to address that gap\.

The broader anomaly\-detection literature provides the conceptual basis for MicroSentryAI\. Foundational surveys organize anomaly detection around recurring methodological families and highlight challenges such as limited labels, high\-dimensional data, low recall, and anomaly explanation\[[7](https://arxiv.org/html/2608.07770#bib.bib8),[21](https://arxiv.org/html/2608.07770#bib.bib9)\]\. Anomalib provides a common algorithmic substrate for unsupervised anomaly detection \(UAD\) by packaging state\-of\-the\-art models together with training, inference, benchmarking, visualization, and hyperparameter tuning\[[3](https://arxiv.org/html/2608.07770#bib.bib10)\]\. Our contribution differs in that it keeps model execution inside an inspector\-facing environment for interactive heatmap visualization, threshold tuning, contour simplification, and direct transfer of AI\-generated masks back into the annotation pipeline\. This emphasis is further motivated by evidence that preprocessing benefits are strongly method\-dependent rather than universal\[[34](https://arxiv.org/html/2608.07770#bib.bib11)\]\.

Evaluation in anomaly detection has progressively shifted from image\-level classification toward fine\-grained spatial localization\. Benchmarks such as MVTec AD and VisA enable this shift by providing pixel\-level annotations and overlap\-based metrics, but they also assume that the original mask is a stable representation of the defect\[[6](https://arxiv.org/html/2608.07770#bib.bib12)\]\. In real industrial settings, expert annotators may agree on the presence and location of a defect while differing on its precise boundary\. For that reason, IoU, precision, and recall remain necessary but not always sufficient, and localization\-oriented measurements such as centroid distance provide a complementary view of agreement\. Our evaluation engine follows that line of work: it serves not only as a scoreboard for ranking models, but also as a calibration layer for comparison against a shared, reproducible spatial definition of a defect\.

## IIIExperimentation

### III\-ADataset and Topologies

To evaluate the efficacy of existing Unsupervised Anomaly Detection \(UAD\) architectures on complex industrial topologies, we conducted our experiments on the “BowTie”\[[18](https://arxiv.org/html/2608.07770#bib.bib1)\]dataset\. The raw acquisition set contains 1,360 labeled images across 10 trays \(1,241 good and 119 reject\)\. Unlike standard benchmarks \(e\.g\., MVTec AD\[[6](https://arxiv.org/html/2608.07770#bib.bib12)\]\), this dataset presents severe real\-world manufacturing challenges, including highly reflective metallic surfaces, microscopic structural defects, and background clutter\. Color profile assignments and counts are summarized in Table[I](https://arxiv.org/html/2608.07770#S3.T1), and representative images from these distinct color profiles are illustrated in Figure[1](https://arxiv.org/html/2608.07770#S3.F1)\. Reported CP1\-CP3 and Combined experiments exclude tray 27952G, using 1,224 images \(1,130 nominal and 94 defect samples\)\.

To align with UAD terminology in the remainder of the paper, we refer to “good” images as nominal and “reject” images as defect samples\.

TABLE I:Label counts and profile assignments for the raw acquisition set\.![Refer to caption](https://arxiv.org/html/2608.07770v1/figures/results/color_profiles.jpg)Figure 1:Representative tray images for CP1–CP3, with excluded tray 27952G shown for contrast\. Tray 27952G is excluded from the benchmark because its color profile and zoom factor are inconsistent with the included trays, and it was later discarded by inspectors\.BowTie is therefore not intended as a replacement for public benchmarks, but as a deployment\-oriented stress test in the sense argued for by recent IAD surveys and benchmark papers\. Recent surveys\[[16](https://arxiv.org/html/2608.07770#bib.bib13)\]note that real manufacturing data often combine subtle defect structure, scarce anomalies, clutter, and domain\-specific acquisition effects, while benchmark analyses\[[30](https://arxiv.org/html/2608.07770#bib.bib14)\]show that model rankings can shift materially once evaluation settings move closer to industrial practice and uniform cross\-family comparisons are enforced\. We use BowTie in that spirit: to test whether Anomalib\-accessible models remain robust under reflective metallic surfaces, profile\-specific appearance shifts, and limited reject support\.

To characterize reject\-class heterogeneity, Table[II](https://arxiv.org/html/2608.07770#S3.T2)summarizes defect\-type counts across CP1\-CP3\. While the dataset contains several anomaly types, representative examples of three common defects are shown in Figure[2](https://arxiv.org/html/2608.07770#S3.F2)\. Gouges \(a, b\) exhibit an elongated, scratch\-like morphology that often blends with specular reflections\. Inclusions \(c, d, e\) appear as isolated surface particles with highly variable size and contrast across color profiles\. Finally, nicks \(f, g\) range from subtle to large edge defects\. Ultimately, this wide morphological diversity complicates precise localization and robust anomaly detection\.

TABLE II:Defect counts for reject images across CP1\-CP3\.![Refer to caption](https://arxiv.org/html/2608.07770v1/figures/results/defect_examples/gouge/121_041.jpg)![Refer to caption](https://arxiv.org/html/2608.07770v1/figures/results/defect_examples/gouge/121_041.jpg)\(a\)
![Refer to caption](https://arxiv.org/html/2608.07770v1/figures/results/defect_examples/gouge/117_100.jpg)![Refer to caption](https://arxiv.org/html/2608.07770v1/figures/results/defect_examples/gouge/117_100.jpg)\(b\)
![Refer to caption](https://arxiv.org/html/2608.07770v1/figures/results/defect_examples/inclusion/121_022.jpg)![Refer to caption](https://arxiv.org/html/2608.07770v1/figures/results/defect_examples/inclusion/121_022.jpg)\(c\)
![Refer to caption](https://arxiv.org/html/2608.07770v1/figures/results/defect_examples/inclusion/27952H_026.jpg)![Refer to caption](https://arxiv.org/html/2608.07770v1/figures/results/defect_examples/inclusion/27952H_026.jpg)\(d\)
![Refer to caption](https://arxiv.org/html/2608.07770v1/figures/results/defect_examples/inclusion/117_086.jpg)![Refer to caption](https://arxiv.org/html/2608.07770v1/figures/results/defect_examples/inclusion/117_086.jpg)\(e\)
![Refer to caption](https://arxiv.org/html/2608.07770v1/figures/results/defect_examples/nick/27952J_059.jpg)![Refer to caption](https://arxiv.org/html/2608.07770v1/figures/results/defect_examples/nick/27952J_059.jpg)\(f\)
![Refer to caption](https://arxiv.org/html/2608.07770v1/figures/results/defect_examples/nick/118_087.jpg)![Refer to caption](https://arxiv.org/html/2608.07770v1/figures/results/defect_examples/nick/118_087.jpg)![Refer to caption](https://arxiv.org/html/2608.07770v1/figures/results/defect_examples/nick/118_087.jpg)\(g\)

Figure 2:Examples of reject\-class defects across CP1\-CP3\. Red boxes indicate defect regions and magnified insets\. Examples include gouges \(a, b\), inclusions \(c, d, e\), and nicks \(f, g\)\.For model benchmarking, we split each color\-profile pool at the image level and train on nominal\-only subsets\. 20% of the nominal pool in each profile was withheld from training and then divided between validation and test, while defect images were excluded from training and split between validation and test within the same profile\. Table[III](https://arxiv.org/html/2608.07770#S3.T3)gives the exact baseline train/validation/test counts used in Section[IV](https://arxiv.org/html/2608.07770#S4)\.

TABLE III:Profile\-wise baseline split counts\. N = nominal and D = defect\. Training uses nominal images only; validation and test contain held\-out nominal images plus defect images from the same profile\.
### III\-BEvaluated Architectures

We evaluated 19 Anomalib\-compatible UAD models\[[3](https://arxiv.org/html/2608.07770#bib.bib10)\]spanning five recurring families: student\-teacher discrepancy methods; patch\-memory / feature\-adaptation methods; flow\-based density estimators; reconstruction\-based methods; and feature\-space density baselines\[[4](https://arxiv.org/html/2608.07770#bib.bib15),[10](https://arxiv.org/html/2608.07770#bib.bib16),[29](https://arxiv.org/html/2608.07770#bib.bib17),[24](https://arxiv.org/html/2608.07770#bib.bib18),[9](https://arxiv.org/html/2608.07770#bib.bib19),[15](https://arxiv.org/html/2608.07770#bib.bib20),[8](https://arxiv.org/html/2608.07770#bib.bib21),[23](https://arxiv.org/html/2608.07770#bib.bib22),[31](https://arxiv.org/html/2608.07770#bib.bib23),[12](https://arxiv.org/html/2608.07770#bib.bib24),[25](https://arxiv.org/html/2608.07770#bib.bib25),[28](https://arxiv.org/html/2608.07770#bib.bib26),[13](https://arxiv.org/html/2608.07770#bib.bib27),[32](https://arxiv.org/html/2608.07770#bib.bib28),[33](https://arxiv.org/html/2608.07770#bib.bib29),[2](https://arxiv.org/html/2608.07770#bib.bib30),[20](https://arxiv.org/html/2608.07770#bib.bib31),[1](https://arxiv.org/html/2608.07770#bib.bib32)\]\. Several entries are hybrids rather than pure exemplars, so these family labels are used as interpretive shorthand rather than as claims that each method instantiates a single mechanism\.

This family\-oriented framing follows the broader IAD literature, which frequently organizes unsupervised methods into recurring mechanism classes and treats family\-level comparisons as more informative than isolated per\-model rankings\[[16](https://arxiv.org/html/2608.07770#bib.bib13),[30](https://arxiv.org/html/2608.07770#bib.bib14)\]\. Keeping BowTie aligned with that taxonomy makes it easier to distinguish broad mechanism behavior from quirks of a single implementation\.

### III\-CImplementation Details

All experiments utilized the Anomalib framework\[[3](https://arxiv.org/html/2608.07770#bib.bib10)\]\. To keep the comparison fair without negating the assumptions made in the original papers, we standardized the data splits, reporting metrics, and early\-stopping policy, but we did not force all methods into a single surrogate anomaly score\. Student\-teacher models retained feature\-discrepancy scoring; patch\-based models retained nearest\-neighbor or patch\-density scoring; flow\-based methods retained likelihood estimation; and reconstruction\-driven methods retained reconstruction or reconstruction\-error outputs\.

Most architectures were trained with a baseline input size of256×256256\\times 256, although a small number of configurations retained a higher configured baseline resolution\. Specifically, U\-Flow and Dinomaly retain a higher configured baseline of448×448448\\times 448due to Anomalib implementation constraints\. The grayscale and resolution settings should therefore be read as controlled sensitivity probes around each model’s configured sweep setting rather than as an attempt to collapse all architectures into an identical preprocessing regime\.

To ensure optimal convergence without overfitting, each configuration used early stopping with a patience of 20 epochs\. BowTie does not include pixel\-level ground\-truth masks, so model selection and threshold selection were both performed at the image level\. F1\-Max denotes the highest F1 score achievable by sweeping all possible decision thresholds; it is used solely to identify the optimal threshold on the validation split\. Macro F1 is then computed at that fixed threshold on the test split, averaging equally over the nominal and anomalous classes to account for the inherent class imbalance between nominal and defective samples\. Each model, profile, and preprocessing setting used the seeded split above\.

We provide code for reproducibility\[[19](https://arxiv.org/html/2608.07770#bib.bib33)\]\.

### III\-DConsensus\-Based Data Audit

After running the full benchmark across the available architectures and the preprocessing ablations discussed in Section[IV](https://arxiv.org/html/2608.07770#S4), we observed that performance repeatedly plateaued below the behavior typically expected on cleaner anomaly\-detection benchmarks\. That pattern suggested that model choice alone was not explaining the remaining error and motivated a secondary audit of nominal\-data quality\. Because the benchmark pipeline already produced inference outputs for every model, we reused those outputs as a diagnostic signal rather than attempting unsupported manual relabeling\.

Each model was therefore run on its nominal training split, producing image\-level anomaly indications for samples that had been treated as normal during optimization\. We then aggregated the model outputs and marked any training image flagged as anomalous by six or more benchmark models as a consensus\-flagged nominal sample\. This six\-model threshold requires cross\-family agreement while keeping the audit conservative for SME triage\. This consensus rule is used solely to prioritize targeted SME review, not to create new labels\. It applies to training\-set predictions only and does not reference test labels\. Because the benchmark includes memory banks, one\-class embeddings, flow likelihood models, and reconstruction\-driven detectors, repeated agreement across families serves here as a practical review signal rather than as a surrogate ground\-truth label\. Reruns that exclude this consensus\-flagged nominal subset from the training pool are interpreted in Section[V](https://arxiv.org/html/2608.07770#S5)as a discussion\-oriented data\-quality analysis rather than as part of the primary benchmark results\.

## IVResults

This section moves from raw scores to operational interpretation\. Table[IV](https://arxiv.org/html/2608.07770#S4.T4)summarizes which architectural families remain reliable on the BowTie dataset at baseline\. The consensus\-based contamination audit described in Section[III\-D](https://arxiv.org/html/2608.07770#S3.SS4)is interpreted in Section[V](https://arxiv.org/html/2608.07770#S5)as a secondary discussion of data quality rather than a primary benchmark result\.

### IV\-AArchitectural Robustness to Complex Industrial Data

BowTie is a challenging benchmark for unsupervised anomaly detection because reflective metallic surfaces, microscopic scratches, and cluttered backgrounds violate the cleaner appearance assumptions that underlie standard benchmarks such as MVTec AD\[[6](https://arxiv.org/html/2608.07770#bib.bib12)\]\. Table[IV](https://arxiv.org/html/2608.07770#S4.T4)therefore serves as the main baseline summary for the cross\-profile comparison, while Figure[3](https://arxiv.org/html/2608.07770#S4.F3)is used afterward as a qualitative check on where those high\-ranking models place their attention\.

Prior work shows that nominal\-data quality, imaging variation, and deployment constraints can reorder methods that appear stable on cleaner benchmarks\[[16](https://arxiv.org/html/2608.07770#bib.bib13),[30](https://arxiv.org/html/2608.07770#bib.bib14)\]\. BowTie extends that perspective to a reflective metal\-inspection setting with explicit cross\-profile appearance shift\.

TABLE IV:Baseline performance across color profiles, grouped by architectural taxonomy\. Best values bold; second\-best values, including ties, underlined\. M\-F1 = Macro F1, A\-F1 = Anomalous F1\. The Combined column reports results from a single training run pooling all three color\-profile subsets into one dataset\.At baseline, several student\-teacher discrepancy models and patch\-level nominal\-support methods appear near the top of the benchmark\. EfficientAD leads CP1 and CP2, PatchCore leads CP3, and Dinomaly is strongest on the Combined baseline\. These baseline rankings indicate that strong BowTie performance is achievable in multiple families, but they do not isolate a single reason for that performance\.

Other families are more profile\-dependent\. Flow models vary sharply: CFlow is excellent on CP1 but weak on CP2, whereas CS\-Flow and U\-Flow are steadier\. Reconstruction\-driven methods are similarly mixed, with Dinomaly strong and DRAEM, DSR, and GANomaly less stable across profiles\. These patterns suggest that model\-specific behavior may matter at least as much as family labels, so the groupings are descriptive rather than mechanistic\.

The anomaly maps in Figure[3](https://arxiv.org/html/2608.07770#S4.F3)complement Table[IV](https://arxiv.org/html/2608.07770#S4.T4)by showing whether the strongest models actually localize defect\-like structure or merely react to specular edges and benign texture shifts\. In the intended workflow, the heatmap provides coarse defect localization and the accompanying SAM masks illustrate how those regions can be refined into inspector\-facing candidate segments for acceptance, rejection, or boundary adjustment; they are not benchmark ground truth\.

![Refer to caption](https://arxiv.org/html/2608.07770v1/figures/results/CP1_anomaly_maps_small.jpg)

![Refer to caption](https://arxiv.org/html/2608.07770v1/figures/results/CP3_anomaly_maps_small.jpg)

Figure 3:EfficientAD detection results on four CP1 \(left\) and four CP3 \(right\) defect samples: originals, heatmaps, overlaid masks, and SAM\-refined proposals\[[22](https://arxiv.org/html/2608.07770#bib.bib34)\]\. In the workflow, heatmaps locate candidate defect vicinity and SAM sharpens regions for inspector acceptance, rejection, or boundary adjustment; these masks are not benchmark ground truth\.
### IV\-BThe Brittleness of Representations

The grayscale and resolution sweeps show that representation stability is architecture\-dependent rather than family\-uniform\. The flow papers in this benchmark all model likelihoods in feature space, but BowTie shows that their sensitivity differs sharply across implementations: CFlow swings from a major loss on CP1 to a major gain on CP2, whereas CS\-Flow and U\-Flow are much less erratic, as shown in Table[V](https://arxiv.org/html/2608.07770#S4.T5)\.

TABLE V:Sensitivity matrix for grayscale \(G\) and resolution scaling \(350×350350\{\\times\}350,448×448448\{\\times\}448\) on the CP1 top\-10 models from Table[VI](https://arxiv.org/html/2608.07770#S5.T6), ranked by CP1 post\-audit Macro F1\. Cells show signedΔ\\DeltaMacro F1 vs\. baseline\.†Models already at448×448448\{\\times\}448in baseline\. Dashes: ablation omitted due to Anomalib limits\.By contrast, PatchCore remains positive under grayscale on CP1 and CP2, and Dinomaly changes only moderately across all three profiles\. Those patterns are consistent with patch\-memory matching and Transformer\-feature representations retaining useful signal when chromatic cues are removed, although this study does not isolate that cause\.

Resolution exposes a different trade\-off\. PatchCore improves at448×448448\\times 448on all three profiles, and Reverse Distillation, STFPM, and AnomalyDINO also gain strongly on the harder profiles\. The underlying papers all emphasize local patch comparison or multiscale feature matching, so these gains are compatible with their published design goals, although BowTie alone does not show whether the improvement comes specifically from finer defect detail, other scale effects, or interactions with the training protocol\[[24](https://arxiv.org/html/2608.07770#bib.bib18),[10](https://arxiv.org/html/2608.07770#bib.bib16),[29](https://arxiv.org/html/2608.07770#bib.bib17),[8](https://arxiv.org/html/2608.07770#bib.bib21)\]\. The flow models again do not move in unison\. CFlow improves on CP2 but degrades on CP1 and CP3, whereas U\-Flow stays closer to baseline\. For industrial deployment, the results support treating grayscale conversion and sensor resolution as model\-specific tuning variables rather than universal preprocessing defaults\.

Taken together, the baseline table and reported ablations show that BowTie performance depends on more than a single leaderboard rank\. EfficientAD, PatchCore, Dinomaly, Reverse Distillation, and CS\-Flow appear among the strongest candidates in the reported experiments, based on baseline rank and observed robustness\. This distinction between rank and stability motivates the data\-quality discussion that follows\.

## VDiscussion

Consistent with recent IAD surveys and benchmark analyses\[[16](https://arxiv.org/html/2608.07770#bib.bib13),[30](https://arxiv.org/html/2608.07770#bib.bib14)\], BowTie shows a relatively consistent performance ceiling across several model families\. That ceiling is informative because the evaluated models encode nominality in very different ways: memory banks store representative normal patches, PaDiM\- and DFM\-style baselines fit feature distributions, student\-teacher methods compress one\-class embeddings, and flow models estimate feature likelihoods\[[24](https://arxiv.org/html/2608.07770#bib.bib18),[9](https://arxiv.org/html/2608.07770#bib.bib19),[1](https://arxiv.org/html/2608.07770#bib.bib32),[10](https://arxiv.org/html/2608.07770#bib.bib16),[12](https://arxiv.org/html/2608.07770#bib.bib24),[25](https://arxiv.org/html/2608.07770#bib.bib25)\]\. When that many mechanisms plateau on the same dataset, architecture alone may not fully explain the remaining error\. Rather than asking non\-experts to relabel marginal cases by hand, we used the model outputs already produced by the benchmark as a diagnostic signal\. As defined in Section[III\-D](https://arxiv.org/html/2608.07770#S3.SS4), the consensus pass therefore serves as a practical audit signal when SME review time is limited\. This interpretation is also compatible with feature\-distribution views of reliability, where repeatedly flagged nominal images can be interpreted as resembling samples near the edge of the learned normal manifold\[[1](https://arxiv.org/html/2608.07770#bib.bib32)\]\.

TABLE VI:Post\-audit comparison after removing the consensus\-flagged nominal subset for the CP1 top\-10 models, ranked by CP1 post\-audit Macro F1\. Cells show post\-audit Macro F1 with relative % change from baseline Macro F1 \(green = improvement, red = degradation; saturation encodes magnitude\)\. Best post\-audit Macro F1 per profile is shown in bold\.Table[VI](https://arxiv.org/html/2608.07770#S5.T6)summarizes what happens when the consensus\-flagged nominal subset identified by the audit is removed and the cleaned reruns are compared against baseline\. The largest gains occur on CP2, the same profile that was most sensitive to grayscale and resolution choices\. The most striking individual result is CFlow, which recovers from very low baseline performance \(Macro F1 = 0\.170\) to 0\.531 after cleaning—a result to interpret cautiously given the small CP2 test support, but one that illustrates why nominal\-data auditing is especially consequential for likelihood\-based architectures\[[12](https://arxiv.org/html/2608.07770#bib.bib24)\]\. That pattern is consistent with an interaction between profile\-specific appearance variation and the consensus\-flagged subset, but it does not by itself establish that these samples materially altered the learned support\. The methods that benefit most, such as PatchCore, Reverse Distillation, CS\-Flow, and Dinomaly, rely on comparatively tight nominal embeddings or likelihood models in their original formulations, so their improvements after cleaning are compatible with that interpretation without proving it\[[24](https://arxiv.org/html/2608.07770#bib.bib18),[10](https://arxiv.org/html/2608.07770#bib.bib16),[25](https://arxiv.org/html/2608.07770#bib.bib25),[13](https://arxiv.org/html/2608.07770#bib.bib27)\]\. Cleaning is not universally helpful, and that is part of the point: some architectures regress after removal of the flagged subset, especially on CP3, suggesting that flagged samples warrant selective review rather than blanket removal\[[32](https://arxiv.org/html/2608.07770#bib.bib28),[33](https://arxiv.org/html/2608.07770#bib.bib29),[2](https://arxiv.org/html/2608.07770#bib.bib30),[12](https://arxiv.org/html/2608.07770#bib.bib24)\]\.

The combined results suggest two practical deployment considerations\. First, preprocessing should be validated jointly with architecture rather than inherited as a default recipe, since grayscale and resolution effects are strongly method\-dependent\[[34](https://arxiv.org/html/2608.07770#bib.bib11)\]\. Second, nominal\-data auditing should be treated as part of model qualification rather than as a one\-time dataset cleanup step, especially when continuous SME review is not available\[[1](https://arxiv.org/html/2608.07770#bib.bib32)\]\. The comparison should be read as a BowTie\-specific stress test rather than as a claim that every model is operating in its ideal published setting\[[8](https://arxiv.org/html/2608.07770#bib.bib21),[13](https://arxiv.org/html/2608.07770#bib.bib27),[4](https://arxiv.org/html/2608.07770#bib.bib15),[30](https://arxiv.org/html/2608.07770#bib.bib14)\]\. Taken together, these findings motivate a workflow in which annotation, inference, and quantitative validation are tightly coupled rather than handled in isolation\.

## VITool Overview

![Refer to caption](https://arxiv.org/html/2608.07770v1/figures/tool-images/workflow_diagram_new.png)Figure 4:AnnoMate & MicroSentryAI human\-in\-the\-loop lifecycleWith the benchmark findings established, this section turns to the software suite initially deployed in the motivating inspection workflow\. Figure[4](https://arxiv.org/html/2608.07770#S6.F4)shows annotation, inference, and validation in one graphical workflow while final accept/reject authority remains with the human inspector\. At submission, the framework was in initial operational testing with inspectors; formal measures of inspection time, consistency, and onboarding effects remain future work\.

### VI\-AArchitecture Summary

The design emphasizes modular, human\-in\-the\-loop inspection\.AnnoMate,MicroSentryAI, and the validation module remain decoupled while exchanging annotations, CSV exports, and Anomalib\-compatible outputs\. Inspectors can review predictions, tune inference parameters, and return accepted AI\-generated masks to annotation without leaving the interface\.

### VI\-BWorkflow Summary

AnnoMateserves as the annotation and curation foundation \(Figure[5](https://arxiv.org/html/2608.07770#S6.F5)\), supporting polygon review, area sorting, review\-status tracking, COCO/VIA export, and overlay generation\. Because reviewed cases, spatial labels, and disposition metadata are stored together, the same interface can support onboarding workflows in which trainees compare decisions against expert\-reviewed reference cases, although that use is outside the current benchmark\.

![Refer to caption](https://arxiv.org/html/2608.07770v1/figures/tool-images/annomate_CP1_void.jpg)Figure 5:TheAnnoMateinterface for defect annotation\. It supports polygon\-based labeling, metadata tracking, and dataset review to streamline ground\-truth curation\.MicroSentryAIadds inference and interactive post\-processing \(Figure[6](https://arxiv.org/html/2608.07770#S6.F6)\)\. It loads trained weights, visualizes normalized anomaly maps, and exposes thresholding, smoothing, and contour controls\. Heatmaps localize suspected defects, while SAM refines those regions into inspector\-facing boundary proposals\[[22](https://arxiv.org/html/2608.07770#bib.bib34)\]\. Inspectors can accept, reject, or adjust candidate segments and separately confirm the image\-level decision before transferring accepted contours back to annotation\. Here, SAM masks illustrate this refinement path rather than benchmark ground truth\.

![Refer to caption](https://arxiv.org/html/2608.07770v1/figures/tool-images/microsentry_CP1_void_vertex.jpg)Figure 6:TheMicroSentryAIinterface for anomaly inference and post\-processing\. A synchronized dual\-view displays the predicted heatmap alongside editable polygon contours, enabling inspectors to localize candidate defects, refine or reject proposed regions, and confirm the overall image\-level decision\.
### VI\-CValidation and Mask Evaluation

![Refer to caption](https://arxiv.org/html/2608.07770v1/figures/results/scratch_002_eval_legendfix.jpg)Figure 7:Mask\-overlap visualization evaluating a PatchCore\[[24](https://arxiv.org/html/2608.07770#bib.bib18)\]model’s spatial accuracy \(pixel AUROC: 0\.989\) on a metal nut from MVTec\. The intersection of ground truth and prediction masks yields an IoU of 0\.673\.The validation module closes the loop by evaluating masks inside the same workflow rather than as disconnected post\-processing\. Figure[7](https://arxiv.org/html/2608.07770#S6.F7)shows mask overlap, and Figure[8](https://arxiv.org/html/2608.07770#S6.F8)shows the evaluation interface using MVTec examples\.111MVTec data\[[6](https://arxiv.org/html/2608.07770#bib.bib12)\]is used here because ground\-truth defect masks for the BowTie dataset were not yet available at the time of article submission\.The engine convertsAnnoMateannotations to binary masks and reports IoU, precision, recall, and centroid distance for model\-vs\.\-ground\-truth validation or user\-vs\.\-model comparison\. These overlays help inspectors and researchers connect numeric scores with defect morphology and annotation ambiguity\.

Together, the three modules operationalize the paper’s core argument: annotation, inference, and quantitative validation are most effective when treated as connected parts of the same inspection process rather than as isolated tasks\.

![Refer to caption](https://arxiv.org/html/2608.07770v1/figures/tool-images/validation_screen_new.jpg)Figure 8:The validation interface for quantitative mask evaluation\. It visually overlays ground\-truth and predicted masks to calculate spatial accuracy metrics, such as Intersection over Union \(IoU\), directly within the workflow, in this case, for a bottle from MVTec\.

## VIIConclusion

This paper examined the gap between anomaly detection benchmark performance and operational reliability in a real\-world industrial setting\. Evaluating 19 unsupervised anomaly detection models on the BowTie dataset, a reflective metallic manufacturing dataset with profile\-specific appearance variation and morphologically diverse defects, we found that no single architecture emerged as uniformly robust\. Preprocessing choices had strongly architecture\-dependent effects, and a consensus\-based data audit indicated that nominal\-data quality further interacts with model sensitivity\. EfficientAD, Dinomaly, PatchCore, Reverse Distillation, and CS\-Flow were the strongest candidates in the reported experiments\.

Motivated by these findings, we presented an initially deployed unified human\-in\-the\-loop framework: AnnoMate for guided annotation and review, MicroSentryAI for AI\-assisted defect localization and segmentation review, and a Validation Engine for mask\-based comparison against expert references where ground truth is available\. Together, the modules replace a prior manual visual inspection and documentation workflow with coupled curation, inference, and quantitative assessment\. MicroSentryAI supports heatmap\-guided localization, SAM\-refined candidates, inspector acceptance or rejection, boundary adjustment, and image\-level confirmation; the Validation Engine reports IoU, precision, recall, and centroid distance\. The same environment also preserves localized decision rationale and can support inspector consistency and onboarding through expert\-reviewed cases, although that use was not evaluated here\.

Because the benchmark uses one real\-world manufacturing dataset and lacked pixel\-level BowTie masks at submission, rankings should be read as a BowTie\-specific stress test rather than general capability claims\. Future work will complete BowTie masks, rerun spatial metrics, measure inspection\-time, consistency, and onboarding effects, and test additional profiles and defect modalities\.

## References

- \[1\]\(2019\)Probabilistic Modeling of Deep Features for Out\-of\-Distribution and Adversarial Detection\.Note:[arXiv:1909\.11786](https://arxiv.org/abs/1909.11786)Cited by:[§III\-B](https://arxiv.org/html/2608.07770#S3.SS2.p1.1),[§V](https://arxiv.org/html/2608.07770#S5.p1.1),[§V](https://arxiv.org/html/2608.07770#S5.p3.1)\.
- \[2\]S\. Akcay, A\. Atapour\-Abarghouei, and T\. P\. Breckon\(2018\)GANomaly: Semi\-Supervised Anomaly Detection via Adversarial Training[\[arXiv\]](https://arxiv.org/abs/1805.06725)\.InACCV,External Links:[Link](https://arxiv.org/abs/1805.06725)Cited by:[§III\-B](https://arxiv.org/html/2608.07770#S3.SS2.p1.1),[§V](https://arxiv.org/html/2608.07770#S5.p2.1)\.
- \[3\]S\. Akcayet al\.\(2022\)Anomalib: A Deep Learning Library for Anomaly Detection[doi: 10\.1109/ICIP46576\.2022\.9897283](https://doi.org/10.1109/ICIP46576.2022.9897283)\.InICIP,pp\. 1706–1710\.External Links:[Document](https://dx.doi.org/10.1109/ICIP46576.2022.9897283)Cited by:[§II](https://arxiv.org/html/2608.07770#S2.p2.1),[§III\-B](https://arxiv.org/html/2608.07770#S3.SS2.p1.1),[§III\-C](https://arxiv.org/html/2608.07770#S3.SS3.p1.1)\.
- \[4\]K\. Batzner, L\. Heckler, and R\. Konig\(2024\)EfficientAD: Accurate Visual Anomaly Detection at Millisecond\-Level Latencies\.InWACV,pp\. 127–137\.Note:[doi: 10\.1109/WACV57701\.2024\.00020](https://doi.org/10.1109/WACV57701.2024.00020)Cited by:[§III\-B](https://arxiv.org/html/2608.07770#S3.SS2.p1.1),[§V](https://arxiv.org/html/2608.07770#S5.p3.1)\.
- \[5\]M\.S\. Benmoussat, M\. Guillaume, Y\. Caulier, and K\. Spinnler\(2013\)Automatic metal parts inspection: use of thermographic images and anomaly detection algorithms\.Infrared Phys\. & Tech\.[doi: 10\.1016/j\.infrared\.2013\.07\.007](https://doi.org/10.1016/j.infrared.2013.07.007)61,pp\. 68–80\.External Links:[Document](https://dx.doi.org/10.1016/j.infrared.2013.07.007)Cited by:[§II](https://arxiv.org/html/2608.07770#S2.p1.1)\.
- \[6\]P\. Bergmann, K\. Batzner, M\. Fauser, D\. Sattlegger, and C\. Steger\(2021\)The MVTec anomaly detection dataset: A comprehensive real\-world dataset for unsupervised anomaly detection\.Int\. J\. Comput\. Vis\.129\(4\),pp\. 1038–1059\.Note:[doi: 10\.1007/s11263\-020\-01400\-4](https://doi.org/10.1007/s11263-020-01400-4)Cited by:[§II](https://arxiv.org/html/2608.07770#S2.p3.1),[§III\-A](https://arxiv.org/html/2608.07770#S3.SS1.p1.1),[§IV\-A](https://arxiv.org/html/2608.07770#S4.SS1.p1.1),[footnote 1](https://arxiv.org/html/2608.07770#footnote1)\.
- \[7\]V\. Chandola, A\. Banerjee, and V\. Kumar\(2009\-07\)Anomaly detection: a survey\.ACM Comput\. Surv\.41\(3\)\.Note:[doi: 10\.1145/1541880\.1541882](https://doi.org/10.1145/1541880.1541882)External Links:[Document](https://dx.doi.org/10.1145/1541880.1541882),ISSN 0360\-0300,[Link](https://doi.org/10.1145/1541880.1541882)Cited by:[§II](https://arxiv.org/html/2608.07770#S2.p2.1)\.
- \[8\]S\. Damm, M\. Laszkiewicz, J\. Lederer, and A\. Fischer\(2025\)AnomalyDINO: Boosting Patch\-based Few\-Shot Anomaly Detection with DINOv2\.InWACV,pp\. 1319–1329\.Note:[doi: 10\.1109/WACV61041\.2025\.00136](https://doi.org/10.1109/WACV61041.2025.00136)Cited by:[§III\-B](https://arxiv.org/html/2608.07770#S3.SS2.p1.1),[§IV\-B](https://arxiv.org/html/2608.07770#S4.SS2.p3.1),[§V](https://arxiv.org/html/2608.07770#S5.p3.1)\.
- \[9\]T\. Defard, A\. Setkov, A\. Loesch, and R\. Audigier\(2021\)PaDiM: a patch distribution modeling framework for anomaly detection and localization\.InICPR Workshops,pp\. 475–489\.Note:[doi: 10\.1007/978\-3\-030\-68799\-1\_35](https://doi.org/10.1007/978-3-030-68799-1_35)Cited by:[§III\-B](https://arxiv.org/html/2608.07770#S3.SS2.p1.1),[§V](https://arxiv.org/html/2608.07770#S5.p1.1)\.
- \[10\]H\. Deng and X\. Li\(2022\)Anomaly detection via reverse distillation from one\-class embedding\.InCVPR,pp\. 9737–9746\.Note:[doi: 10\.1109/CVPR52688\.2022\.00951](https://doi.org/10.1109/CVPR52688.2022.00951)Cited by:[§III\-B](https://arxiv.org/html/2608.07770#S3.SS2.p1.1),[§IV\-B](https://arxiv.org/html/2608.07770#S4.SS2.p3.1),[§V](https://arxiv.org/html/2608.07770#S5.p1.1),[§V](https://arxiv.org/html/2608.07770#S5.p2.1)\.
- \[11\]A\. Dutta and A\. Zisserman\(2019\)The via annotation software for images, audio and video\.InACM Multimedia[doi: 10\.1145/3343031\.3350535](https://doi.org/10.1145/3343031.3350535),External Links:[Document](https://dx.doi.org/10.1145/3343031.3350535)Cited by:[§II](https://arxiv.org/html/2608.07770#S2.p1.1)\.
- \[12\]D\. Gudovskiy, S\. Ishizaka, and K\. Kozuka\(2022\)CFLOW\-AD: Real\-Time Unsupervised Anomaly Detection with Localization via Conditional Normalizing Flows\.InWACV,pp\. 1819–1828\.Note:[doi: 10\.1109/WACV51458\.2022\.00188](https://doi.org/10.1109/WACV51458.2022.00188)Cited by:[§III\-B](https://arxiv.org/html/2608.07770#S3.SS2.p1.1),[§V](https://arxiv.org/html/2608.07770#S5.p1.1),[§V](https://arxiv.org/html/2608.07770#S5.p2.1)\.
- \[13\]J\. Guoet al\.\(2025\)Dinomaly: The Less Is More Philosophy in Multi\-Class Unsupervised Anomaly Detection\.InCVPR,pp\. 20405–20415\.Note:[paper: CVPR OA](https://openaccess.thecvf.com/content/CVPR2025/html/Guo_Dinomaly_The_Less_Is_More_Philosophy_in_Multi-Class_Unsupervised_Anomaly_CVPR_2025_paper.html)Cited by:[§III\-B](https://arxiv.org/html/2608.07770#S3.SS2.p1.1),[§V](https://arxiv.org/html/2608.07770#S5.p2.1),[§V](https://arxiv.org/html/2608.07770#S5.p3.1)\.
- \[14\]F\. Kajiet al\.\(2022\)A deep\-learning\-based in\-situ surface anomaly detection methodology for laser directed energy deposition via powder feeding\.J\. Manuf\. Process\.[doi: 10\.1016/j\.jmapro\.2022\.06\.046](https://doi.org/10.1016/j.jmapro.2022.06.046)81,pp\. 624–637\.External Links:[Document](https://dx.doi.org/10.1016/j.jmapro.2022.06.046)Cited by:[§II](https://arxiv.org/html/2608.07770#S2.p1.1)\.
- \[15\]S\. Lee, S\. Lee, and B\. C\. Song\(2022\)CFA: coupled\-hypersphere\-based feature adaptation for target\-oriented anomaly localization\.IEEE Access10,pp\. 78446–78454\.Note:[doi: 10\.1109/ACCESS\.2022\.3193699](https://doi.org/10.1109/ACCESS.2022.3193699)External Links:[Link](https://ieeexplore.ieee.org/stamp/stamp.jsp?%0Aarnumber=9839549)Cited by:[§III\-B](https://arxiv.org/html/2608.07770#S3.SS2.p1.1)\.
- \[16\]J\. Liuet al\.\(2024\)Deep industrial image anomaly detection: a survey\.Mach\. Intell\. Res\.21\(1\),pp\. 104–135\.Note:[doi: 10\.1007/s11633\-023\-1459\-z](https://doi.org/10.1007/s11633-023-1459-z)Cited by:[§III\-A](https://arxiv.org/html/2608.07770#S3.SS1.p3.1),[§III\-B](https://arxiv.org/html/2608.07770#S3.SS2.p2.1),[§IV\-A](https://arxiv.org/html/2608.07770#S4.SS1.p2.1),[§V](https://arxiv.org/html/2608.07770#S5.p1.1)\.
- \[17\]Los Alamos National Laboratory\(2026\)AnnoMate with microsentryai: human\-in\-the\-loop aiml\-powered inspection tools\.Note:[https://github\.com/lanl/annomate\-microsentryai\-workflow](https://github.com/lanl/annomate-microsentryai-workflow)GitHub repository, accessed April 2026Cited by:[§I](https://arxiv.org/html/2608.07770#S1.p4.1)\.
- \[18\]Los Alamos National Laboratory\(2026\)Oceans 11 Data Repository\.Note:[https://oceans11\.lanl\.gov](https://oceans11.lanl.gov/)Accessed: Apr\. 13, 2026Cited by:[§I](https://arxiv.org/html/2608.07770#S1.p2.1),[§III\-A](https://arxiv.org/html/2608.07770#S3.SS1.p1.1)\.
- \[19\]Los Alamos National Laboratory\(2026\)Repository for reproducibility for ICMLA 2026\.Note:[https://tinyurl\.com/placeholder](https://tinyurl.com/placeholder)Accessed: 2026Cited by:[§III\-C](https://arxiv.org/html/2608.07770#S3.SS3.p4.1)\.
- \[20\]I\. Ndiour, N\. Ahuja, U\. Genc, and O\. Tickoo\(2022\)FRE: A Fast Method For Anomaly Detection And Segmentation[\[arXiv\]](https://arxiv.org/abs/2211.12650)\.External Links:[Link](https://arxiv.org/abs/2211.12650)Cited by:[§III\-B](https://arxiv.org/html/2608.07770#S3.SS2.p1.1)\.
- \[21\]G\. Pang, C\. Shen, L\. Cao, and A\. V\. D\. Hengel\(2021\-03\)Deep Learning for Anomaly Detection: A Review[doi: 10\.1145/3439950](https://doi.org/10.1145/3439950)\.ACM Comput\. Surv\.\(2\)\.External Links:[Document](https://dx.doi.org/10.1145/3439950),ISSN 0360\-0300,[Link](https://doi.org/10.1145/3439950)Cited by:[§II](https://arxiv.org/html/2608.07770#S2.p2.1)\.
- \[22\]N\. Raviet al\.\(2025\)SAM 2: Segment Anything in Images and Videos\.InICLR,Note:[paper: OpenReview](https://openreview.net/forum?id=Ha6RTeWMd0)Cited by:[Figure 3](https://arxiv.org/html/2608.07770#S4.F3),[Figure 3](https://arxiv.org/html/2608.07770#S4.F3.3.2),[§VI\-B](https://arxiv.org/html/2608.07770#S6.SS2.p2.1)\.
- \[23\]B\. Rolih, M\. Fučka, and D\. Skočaj\(2025\)SuperSimpleNet: Unifying Unsupervised and Supervised Learning for Fast and Reliable Surface Defect Detection\.InPattern Recognit\.,pp\. 47–65\.Note:[arXiv:2408\.03143](https://arxiv.org/abs/2408.03143)Cited by:[§III\-B](https://arxiv.org/html/2608.07770#S3.SS2.p1.1)\.
- \[24\]K\. Roth, L\. Pemula, J\. Zepeda, B\. Scholkopf, T\. Brox, and P\. Gehler\(2022\)Towards Total Recall in Industrial Anomaly Detection\.InCVPR,pp\. 14318–14328\.Note:[doi: 10\.1109/CVPR52688\.2022\.01392](https://doi.org/10.1109/CVPR52688.2022.01392)Cited by:[§III\-B](https://arxiv.org/html/2608.07770#S3.SS2.p1.1),[§IV\-B](https://arxiv.org/html/2608.07770#S4.SS2.p3.1),[§V](https://arxiv.org/html/2608.07770#S5.p1.1),[§V](https://arxiv.org/html/2608.07770#S5.p2.1),[Figure 7](https://arxiv.org/html/2608.07770#S6.F7),[Figure 7](https://arxiv.org/html/2608.07770#S6.F7.3.2)\.
- \[25\]M\. Rudolph, T\. Wehrbein, B\. Rosenhahn, and B\. Wandt\(2022\)Fully Convolutional Cross\-Scale\-Flows for Image\-based Defect Detection\.InWACV,pp\. 1829–1838\.Note:[doi: 10\.1109/WACV51458\.2022\.00189](https://doi.org/10.1109/WACV51458.2022.00189)Cited by:[§III\-B](https://arxiv.org/html/2608.07770#S3.SS2.p1.1),[§V](https://arxiv.org/html/2608.07770#S5.p1.1),[§V](https://arxiv.org/html/2608.07770#S5.p2.1)\.
- \[26\]B\. C\. Russell, A\. Torralba, K\. P\. Murphy, and W\. T\. Freeman\(2008\)LabelMe: a database and web\-based tool for image annotation\.Int\. J\. Comput\. Vis\.[doi: 10\.1007/s11263\-007\-0090\-8](https://doi.org/10.1007/s11263-007-0090-8)77\(1–3\),pp\. 157–173\.External Links:[Document](https://dx.doi.org/10.1007/s11263-007-0090-8)Cited by:[§II](https://arxiv.org/html/2608.07770#S2.p1.1)\.
- \[27\]T\. Saharet al\.\(2023\)Anomaly detection in laser powder bed fusion using machine learning: a review\.Results Eng\.[doi: 10\.1016/j\.rineng\.2022\.100803](https://doi.org/10.1016/j.rineng.2022.100803)17\.External Links:[Document](https://dx.doi.org/10.1016/j.rineng.2022.100803)Cited by:[§II](https://arxiv.org/html/2608.07770#S2.p1.1)\.
- \[28\]M\. Tailanian, Á\. Pardo, and P\. Musé\(2024\)U\-Flow: a u\-shaped normalizing flow for anomaly detection with unsupervised threshold\.J\. Math\. Imaging Vis\.66\(4\),pp\. 678–696\.Note:[doi: 10\.1007/s10851\-024\-01193\-y](https://doi.org/10.1007/s10851-024-01193-y)Cited by:[§III\-B](https://arxiv.org/html/2608.07770#S3.SS2.p1.1)\.
- \[29\]G\. Wang, S\. Han, E\. Ding, and D\. Huang\(2021\)Student\-teacher feature pyramid matching for anomaly detection\.InBMVC,Note:[doi: 10\.5244/C\.35\.349](https://doi.org/10.5244/C.35.349)External Links:[Link](https://arxiv.org/abs/2103.04257)Cited by:[§III\-B](https://arxiv.org/html/2608.07770#S3.SS2.p1.1),[§IV\-B](https://arxiv.org/html/2608.07770#S4.SS2.p3.1)\.
- \[30\]G\. Xieet al\.\(2024\)IM\-IAD: industrial image anomaly detection benchmark in manufacturing\.InCVPR,Note:[arXiv:2301\.13359](https://arxiv.org/abs/2301.13359)External Links:[Link](https://arxiv.org/abs/2301.13359)Cited by:[§III\-A](https://arxiv.org/html/2608.07770#S3.SS1.p3.1),[§III\-B](https://arxiv.org/html/2608.07770#S3.SS2.p2.1),[§IV\-A](https://arxiv.org/html/2608.07770#S4.SS1.p2.1),[§V](https://arxiv.org/html/2608.07770#S5.p1.1),[§V](https://arxiv.org/html/2608.07770#S5.p3.1)\.
- \[31\]J\. Yu, Y\. Zheng, X\. Wang, W\. Li, Y\. Wu, R\. Zhao, and L\. Wu\(2021\)FastFlow: Unsupervised Anomaly Detection and Localization via 2D Normalizing Flows\.Note:[arXiv:2111\.07677](https://arxiv.org/abs/2111.07677)Cited by:[§III\-B](https://arxiv.org/html/2608.07770#S3.SS2.p1.1)\.
- \[32\]V\. Zavrtanik, M\. Kristan, and D\. Skocaj\(2021\)DRÆM – A discriminatively trained reconstruction embedding for surface anomaly detection\.InICCV,pp\. 8310–8319\.Note:[doi: 10\.1109/ICCV48922\.2021\.00822](https://doi.org/10.1109/ICCV48922.2021.00822)Cited by:[§III\-B](https://arxiv.org/html/2608.07770#S3.SS2.p1.1),[§V](https://arxiv.org/html/2608.07770#S5.p2.1)\.
- \[33\]V\. Zavrtanik, M\. Kristan, and D\. Skočaj\(2022\)DSR – a dual subspace re\-projection network for surface anomaly detection\.InECCV,pp\. 539–554\.Note:[doi: 10\.1007/978\-3\-031\-19821\-2\_31](https://doi.org/10.1007/978-3-031-19821-2%5F31)Cited by:[§III\-B](https://arxiv.org/html/2608.07770#S3.SS2.p1.1),[§V](https://arxiv.org/html/2608.07770#S5.p2.1)\.
- \[34\]L\. Zhanget al\.\(2023\)What makes a good data augmentation for few\-shot unsupervised image anomaly detection?\.Note:[arXiv:2304\.03294](https://arxiv.org/abs/2304.03294)External Links:[Link](https://arxiv.org/abs/2304.03294)Cited by:[§II](https://arxiv.org/html/2608.07770#S2.p2.1),[§V](https://arxiv.org/html/2608.07770#S5.p3.1)\.

Similar Articles

Anomalies in Multivariate Time Series Benchmarks Are Mostly Univariate

arXiv cs.LG

This paper introduces a diagnostic framework for multivariate time series anomaly detection benchmarks and finds that labeled anomalies are mostly detectable from individual channels, challenging the need for cross-channel modeling. The authors call for more structurally diverse evaluation sets.