- Rating
- 2
- Confidence
- 4
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
This paper proposes AGENTICAD, a two-stage framework for sample-adaptive industrial anomaly detection. Stage I learns a lightweight controller to select one of four frozen anomaly detection experts based on image features. Stage II employs another controller to adaptively select image transformations or stop further inspection, using AnomalyCLIP as a frozen local detector. Both controllers are trained with full-information supervision derived from labeled anomaly data.
The authors construct IND-COM by combining five existing industrial anomaly detection datasets and adopting a supervised-controller training protocol. The method achieves 91.34% image-level AUROC and 92.45% pixel-level AUROC. While the results demonstrate the potential of adaptive inspection, I have concerns about the supervision-matched comparisons, the contributions of individual components, and the reliability of certain baseline results.
Critical strengths
The authors provide an insightful observation that different anomaly detection experts exhibit distinct strengths across anomaly types, even within the same object category, as illustrated in Figure 1(A).
Critical weaknesses
- Limited supervision-matched comparisons and insufficient evidence of the advantage over simpler supervised alternatives.
A major concern is the experimental protocol. AGENTICAD trains its controllers using 7,316 labeled images, including 5,299 anomalous images, and additionally uses pixel-level annotations for localization. In contrast, conventional UAD baselines are trained using only normal images. Although the authors acknowledge this difference, comparisons against unsupervised methods cannot adequately establish the advantage of the proposed framework under comparable supervision.
Moreover, the improvement of Stage I over strong unsupervised baselines appears relatively modest on MVTec AD. As shown in Table 2, Stage I achieves 94.56% image-level AUROC, only 0.90 percentage points higher than Dinomaly (93.66%), while remaining below Dinomaly2 (97.20%). Even the complete Stage II framework (96.35%) does not outperform Dinomaly2 on this dataset. These results raise questions about whether the performance gains justify the substantial additional labeled training data required by the proposed framework.
Since substantial anomaly supervision is already available, comparisons with lightweight supervised classifiers or segmentation models trained using the same annotations would be important for demonstrating the practical value of the proposed control-based approach.
- Incomplete component analysis and concerns about baseline reliability.
Although Table 5 includes fixed-observation baselines, the contribution of Stage I routing to the complete system remains insufficiently isolated. In particular, it is unclear whether applying the same Stage II observation controller directly to a strong individual detector, such as Dinomaly, could achieve comparable performance. The generality of Stage II is also unclear because AnomalyCLIP is the only generic local detector evaluated. Furthermore, Tables 2 and 3 do not report the standalone performance of AnomalyCLIP.
I am also concerned about the unexpectedly low results of DeCo-Diff. Table 2 reports only 44.71% image-level AUROC on MVTec AD, while the official DeCo-Diff repository reports approximately 99.3% under its original evaluation setting. Although the evaluation protocols differ, such a substantial discrepancy requires careful verification of the implementation, anomaly-score direction, preprocessing, and evaluation procedure.
Questions for authors
Q1. Supervision-matched comparisons. Given that AGENTICAD uses thousands of labeled anomalous images and pixel-level masks, could the authors compare against simple supervised classification and segmentation baselines trained using the same annotation budget? How much of the improvement is attributable to the proposed adaptive control mechanism rather than access to additional anomaly supervision?
Q2. Contribution of Stage I and generality of Stage II. What performance would be achieved by applying the same Stage II training and inference strategy directly to Dinomaly, without Stage I routing? Could the authors also evaluate Stage II using another frozen local detector instead of AnomalyCLIP? Reporting the standalone image-level and pixel-level performance of AnomalyCLIP would further clarify its contribution.
Q3. DeCo-Diff baseline. Could the authors explain the very low DeCo-Diff performance in Tables 2 and 3, especially on MVTec AD? The reported values differ substantially from those in the original work and official implementation. Please clarify the implementation, checkpoint, preprocessing, anomaly-score direction, and evaluation settings.