- Rating
- 3
- Confidence
- 4
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 3
Read review
Paper summary
This paper introduces ADPretrain++, an improved method of ADPretrain, aimed at providing specialized pre-trained representations for the anomaly detection field. Compared to ADPretrain, ADPretrain++ mainly makes two improvements: Firstly, it sets the encoder to be learnable, offering a higher parameter capacity compared to the fixed encoder in ADPretrain. Secondly, it introduces two additional branches, namely the image adapter and the pixel adapter. These two branches are specifically designed for image-level detection and pixel-level localization, respectively, achieving superior performance compared to the shared projector for their respective tasks. The pixel adapter is trained with a dense norm-map loss and prototype shaping, the image adapter incorporates top-k multi-instance learning and descriptor shaping. Experimental results on multiple downstream datasets and anomaly detection methods demonstrate the improvement of pre-trained representations obtained by ADPretrain++ over ADPretrain.
Critical strengths
-
The problem addressed in this paper is of great value: constructing dedicated pre-trained representations for the anomaly detection field, thereby empowering all anomaly detection methods in the entire field. ADPretrain++ further demonstrates that residual features can serve as the fundamental representation in the anomaly detection field.
-
The pre-trained features constructed by ADPretrain++ have achieved consistent improvements over ADPretrain on multiple downstream datasets and downstream anomaly detection methods, further advancing the progress in the direction of anomaly representation pre-training.
Critical weaknesses
-
Is Lora used in every layer of the encoder, or is it only applied in the layers that output features? In line 151, it mentions "the last four blocks". If it refers to the last four blocks of the entire encoder, this would mean that the features output from the previous three levels are still based on a fixed encoder without Lora.
-
Setting the encoder to learnable or using LoRa in ADPretrain can lead to training failures. However, using LoRa in ADPretrain++ achieved good results. How was this achieved? Is there a specific method to avoid training failures? Have you ever tried setting the entire encoder to learnable? What was the effect?
-
Compared to ADPretrain, ADPretrain++ introduces an additional 4 losses, making a total of 6 losses. There are too many losses, causing the method complex, is it possible to simplify them? In Table 2, some losses actually do not bring much effect, and could be considered for removal. The problem with having 6 losses is that the weighting factor for each loss cannot be adjusted at all, requiring extensive hyperparameter experiments. However, the paper does not provide any hyperparameter experiments for the weight parameters of the losses.
-
Although the paper emphasizes that separating the image and pixel paths is a more optimal approach, in practice, only the representations from these two paths are used simultaneously in PatchCore, while only the pixel path is employed in other methods. Therefore, the experimental support for the core idea in the paper is insufficient. Additionally, if image-level detection and pixel-level localization utilize two different feature paths, do these downstream AD methods need to model and train twice with different features? In this case, the two feature paths actually have little significance.
-
The experimental verification using only DINO-v3-L as a backbone is insufficient. In ADPretrain, verification was conducted on a total of 5 backbones. As a pre-training representation task, the core value is to provide better pre-training representations. Therefore, pre-training is necessary on all current mainstream backbones used for anomaly detection to provide good representations. Additionally, the current input resolution is 224x224, but some of the latest AD methods use higher resolutions such as 448x448. Therefore, it is best to provide a larger model than DINO-v3-L and pre-training representations at a higher resolution.
-
In Table 2, the effect of using only one route is already quite good. So what is the significance of using two routes? AUPRO even decreases.
Questions for authors
The questions have been written in the Weaknesses part.