- Rating
- 2
- Confidence
- 4
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
The paper proposes EVoSAE, which uses BatchTopK SAE to decompose DINOv2 dense patch features into sparse "semantic atoms" and construct atom level normal memory. During testing, soft normal weights are constructed based on reconstruction errors, and SAE is continuously fine tuned to allow memory to evolve on the flow test samples.
Critical strengths
The proposed method is simple and is easy to follow, and show the promising results on datasets.
Critical weaknesses
Poor clarity and rigor. In the paper, there are many symbols that are inconsistent, such as Eq (1) and line 141 and Eq. (5) and line 200. "x" is not uniform. In Eq. (6), what is g_theta? It is not explained. Besides, there are many format issues that can affect readability, such as lines 198-199, lines 206-207, and so on. Besides, in References, there are multiple same references introduced, such as lines 547-553, lines 604-610, and so on. Overall, many minor issues lead to a big problem.
Unfair comparison. In the paper, the DINOv2-G is used, which is a large model. However, the results of baselines are from the original papers, where baselines' feature extraction is based on DINOv2-B, DINOv2-L, or other backbones. So, different backbones affect results. From the Appendix, it is found that DINOv2-B or DINOv2-L for the proposed method is not superior to existing methods. Thus, it is recommended to use the same backbones to conduct experiments, for fair comparison. Overall, the proposed method is simple but relies on pre-trained networks.
Memory overhead. The proposed method constructs normal memory that consists of the learned decoder directions of an SAE. Please report the memory storage compared with existing feature-level-based memory construction methods to show the advantage.
Questions for authors
See weakness. The main issues include poor clarity and rigor and potential unfair comparison. Besides, it is recommended to report memory overhead due to the claimed non-feature-level memory construction. The rating will be reconsidered during rebuttal.
4 comments
Thank you for your effort and response. The response has addressed some of my concerns. The proposed method is simple-effective, but it still incurs increased memory overhead despite the proposed atom-level memory.
Besides, please upload the new PDF version, since the current PDF is still the previous one, which makes me hard to tell the clarity and rigor of the paper.
We sincerely thank you for your response and valuable suggestions, which have helped us improve the quality of our submission.
We would like to clarify two points:
-
During the rebuttal period, we conducted extensive additional experiments, some of which required substantial computational time. Therefore, we did not update our paper at our first rebuttal. We have now uploaded a revised version that corrects typos, mathematical notation inconsistencies, formatting issues, and unclear descriptions. All modifications are highlighted in blue for ease of reference. We would greatly appreciate it if you could review the updated manuscript.
-
In fact, Our atom-level memory requires less storage than the feature-based memory of AnomalyDINO (288.19 MiB vs. 432.28 MiB), achieving a 33.3% reduction. Note that SubspaceAD is not a feature memory-bank-based method; instead, it employs a compact PCA subspace to reconstruct test features, resulting in a smaller memory footprint. Although our method requires additional GPU memory for test-time adaptation, it achieves a favorable trade-off between memory efficiency and anomaly detection performance.
Thank you for your response. The newly uploaded PDF addresses most of my concerns. However, the overhead (memory and even inference time) is still a major concern. The memory overhead should have been much smaller as expected, due to atom-level memory construction. But it still incur over hundreds of MiB. Besides, the performance of the proposed method mainly depends on pre-trained feature extractors (e.g., DINO series) like many existing FSAD methods. Thus, in this case, the proposed method may lack competitiveness if it has no edge in computational efficiency.
Rebuttal by Authors
We thank Reviewer LgQ4 for your insightful comments and suggestions! We appreciate your positive reviews on the simple idea and promising results. Below are our point-to-point clarifications to address your concerns. Feel free to discuss with us if you have further questions!
We sincerely thank the reviewer for your careful reading and constructive feedback. We will carefully correct the notation inconsistencies, typos, references, and related descriptions in the revised manuscript.
We sincerely apologize to the reviewer for the confusion caused by the incorrectly reported baseline results. This was an oversight on our part. Since SubspaceAD is the most closely related and competitive baseline, we followed its experimental configuration, including the DINOv2-G backbone and random seeds. However, we directly adopted the results of AnomalyDINO and other baselines from SubspaceAD without double checking. To address this issue, we have now included the results of AnomalyDINO evaluated with DINOv2-G and corrected the corresponding comparisons. We will update Table 1 accordingly once the remaining baseline evaluations are completed.
Following the reviewer's suggestion, we report the normal memory storage and peak GPU memory usage below.
1) Normal Memory Storage. AnomalyDINO stores dense patch features, resulting in the largest memory footprint. In contrast, SubspaceAD uses a compact PCA subspace and achieves the lowest storage cost. EvoSAE employs an SAE-based atom-level memory, reducing storage by 33.3% compared with AnomalyDINO, although requiring more storage than SubspaceAD.
2) Peak GPU Memory. AnomalyDINO achieves the lowest peak GPU memory usage through feature matching without parameter updates. In contrast, SubspaceAD requires additional computation for PCA-based reconstruction, and EvoSAE incurs memory overhead from gradient-based SAE adaptation. EvoSAE uses slightly more peak GPU memory than SubspaceAD (28.04 vs. 25.59 GiB).
3) Performance Trade-off. Despite its additional adaptation overhead, EvoSAE achieves the best results in 3 out of 4 metrics, demonstrating the effectiveness of its evolving atom-level memory for few-shot anomaly detection.
Table: Efficiency and detection performance comparison on MVTec-AD under the 4-shot setting. Best results are highlighted in bold.