- Rating
- 1
- Confidence
- 2
- Informativeness
- 1
- Presentation
- 1
- Soundness
- 2
Read review
Paper summary
The paper studies the question of "when does the volume-change correction carry anomaly information beyond the Gaussian endpoint, and what is lost by omitting it" in the context of flow-matching anomaly detection for (industrial) images.
By comparing the endpoint-only, correction-only, and full scores of FlowAD, they conclude that dropping the correction costs pixel-level localization accuracy, while image-level detection is largely unaffected or slightly improved.
Critical strengths
The experiments show that the practice of dropping the divergence term in existing methods might be problematic.
Critical weaknesses
-
The problem statement of when the divergence term can be omitted is meaningful by itself, but the paper studied this problem mostly empirically with one model family (albeit across two backbones and three datasets). This makes the paper a bit shallow, i.e., no novel or interesting insight was revealed about why we cannot omit the divergence term.
-
While a condition is given in Proposition 1 that describes a case where the divergence term can be omitted theoretically, this result feels isolated from the empirical results which mainly show that the divergence term is needed for localization.
-
Although the third point in the contribution list highlights that FlowAD exceeds PatchCore by 2.46 P-AUPRO points on VisA, this comparison is selective. In Table 4(c), PatchCore, which requires no training, achieves the best result in half of the twelve columns, including image AUROC on all three datasets, and no single FlowAD configuration is consistently better.
-
Overall, the contribution is limited. The method combines existing components (flow matching, Hutchinson estimation, frozen pretrained features), the theoretical result covers only a Gaussian case that does not bear on the empirical findings, and the empirical finding itself is not explained or turned into a design principle.
Questions for authors
As the third point of the contribution list states that the authors "introduce FlowAD, a flow-matching method that detects and localizes anomalies ...", would the authors kindly clarify which components of FlowAD, apart from the finite-difference trace estimator, are new / designed by them? If most components are from existing methods, what are the contributions / challenges in making it work?
2 comments
I thank the authors for the additional analyses and for clarifying the paper’s intended contribution. The revised PatchCore comparison addresses W3 by reporting where each method performs better, but in general I am not fully convinced that my concerns have been addressed.
For W1, my question was why retaining the divergence term improves localization in the settings studied. The additional analyses clarify how the gains vary with layer fusion, though I still find it unclear why the correction helps identify defective regions.
For W2, I appreciate the connection the authors draw between Proposition 1 and changes in score rankings. My remaining concern is that it is still unclear how the Gaussian result helps explain the observed localization gains.
Regarding W4 and Q1, I asked which components of FlowAD the authors designed beyond the finite-difference trace estimator and what challenges arose in combining the established components. The response clarifies that the authors regard the controlled comparison of scoring rules as their main contribution. It also explains the computational problem addressed by the estimator. Beyond that estimator, the response does not identify an additional component the authors designed or a specific challenge in combining the remaining components.
Response to Reviewer WH87
Thank you for identifying the need to connect the analysis to the empirical findings. We have strengthened that connection and clarified the contribution and benchmark comparisons.
The revised paper explains this distinction through ranking margins and spatial aggregation rather than score magnitude alone. The Gaussian case identifies an exact ranking-preserving limit; Sections 5.2–5.4 connect it to image-pair reversals, common localization errors and fitted-density comparisons. Forward-only finite-difference evaluation makes the correction accessible without differentiation through the field. We quantify its agreement and cost against shared-probe automatic differentiation. The FM objective, CNF identity and Hutchinson principle are established; our claims concern their implications for anomaly scoring.
For image-max scoring, qi=Vi(pE(i))+ri, where pE is the endpoint maximum and ri≥0 is the gain from spatial reselection. Section 5.2 applies this identity to 96,200 within-category pairs per cohort. No ties occur in these cohorts. Category-macro repair minus harm reproduces the AUROC change: -0.6532 points for C-RADIO L31 and +1.2417 for DINOv3. At 5% FPR, Section 5.3 shows that smaller fusion gains can coexist with greater recovery on common endpoint errors. These analyses connect the ranking criterion to measured outcomes; they do not identify a causal mechanism of pretraining. The C-RADIO fusion models are distinct from Table 1's three-seed models.
In a separate 12-category budget control, normal-training FM MSE falls in every category from 30 to 120 epochs, while E P-AUPRO falls from 85.85 to 83.41 and image AUROC rises from 91.92 to 93.63. Lower measured FM error does not imply better localization rankings. These seed-0 runs use separate cosine schedules and in-sample MSE, not a convergence test. Eight categories use re-extracted features and new models; scores share features within each category. The Gaussian proposition is a population reference, not a finite-network guarantee.
Table 4 separately compares recent flow-based methods under their native protocols. These results provide context, not a controlled ranking across papers. Section 5.6 also reports matched max-after-fusion PatchCore scores on all 57 categories. VisA image AUROC ties five-layer FlowAD at two decimals; FlowAD retains a 2.46-point P-AUPRO advantage. PatchCore leads image AUROC on MVTec AD/Real-IAD and P-AUPRO on MVTec AD. Layer selection, normalization and fusion still differ. We now foreground both the fitted-density comparison and these task-specific trade-offs rather than using one metric to imply general dominance.