- Rating
- 2
- Confidence
- 4
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 3
Read review
Paper summary
This paper presents a very clear approach to anomaly-aware counting in industrial scenes. The method first localizes multiple ROIs in an image, then compares local features across different instances in the same scene to highlight regions that deviate from the others, allowing the model to distinguish intact from defective instances and count them accordingly. The overall idea is straightforward and easy to follow, and the authors also build a relatively large Real-ZAC dataset and conduct extensive experiments.
Critical strengths
- A major strength is the real industrial setting and the large dataset, which gives the experiments solid support.
- The core idea also makes a lot of sense for this problem, and the experiments show that it works well.
Critical weaknesses
A key weakness is the limited novelty. Recent work such as MuSc and Odd-One-Out already uses very similar ideas based on mutual matching or cross-instance comparison, so this paper currently feels more like applying an effective existing idea to a new industrial setting.
What I would really like to see is stronger evidence that the method learns a genuinely different representation for this task. For example, showing that the learned features become more defect-sensitive and less dominated by object identity, rather than just improving performance through a known comparison strategy.
Questions for authors
-
Could the authors clarify the key algorithmic novelty of Pinpoint beyond prior comparative anomaly-detection methods such as MuSc and Odd-One-Out? In particular, what new capability or representation is introduced here, rather than adapting an existing cross-instance comparison idea to a new setting?
-
Can the authors provide stronger evidence that Pinpoint actually learns a different representation for defect state? For example, it would be useful to show whether the learned features become more defect-sensitive and less dominated by object identity after adding the comparative descriptor and within-image centering.
-
For the ObjEmbed baseline in Table 2, does it use exactly the same CountGD++ proposals and the same training setup as Pinpoint? Since the paper shows that proposal quality has a large effect on performance, this detail is important for understanding how much of the gain comes from the proposed representation itself.
8 comments
Q2.
| Setting | MAE ↓ | RMSE ↓ | ↑ |
|---|---|---|---|
| Representation components (validation-selected threshold) | |||
| ObjEmbed fine-tuned (original recipe) | 2.73 | 3.70 | .802 |
| + LoRA with focal loss | 2.40 | 3.49 | .834 |
| + DINOv3 comparative descriptor | 2.62 | 3.86 | .843 |
| + within-image centering | 1.97 | 3.04 | .872 |
| + magnitude restoration (Pinpoint) | 1.93 | 3.02 | .876 |
| Pinpoint, inference rule | |||
| Validation-selected threshold | 1.93 | 3.02 | .876 |
| Argmax (, no calibration) | 2.09 | 3.29 | .872 |
| Plain DINOv3 ROI feature (no mutual scoring) | |||
| ROI feature, validation-selected threshold | 2.51 | 3.65 | .837 |
| + centering | 2.17 | 3.27 | .858 |
| ROI feature, argmax () | 2.46 | 3.73 | .849 |
| + centering | 2.46 | 3.69 | .855 |
We have extended Table 10 (Table 11 in the revision) with plain DINOv3 ROI-feature rows, so that each component is isolated under identical proposals and training. Within-image centering subtracts the median descriptor of the image. This removes the appearance shared by all instances of the same object and keeps only how each instance deviates from the others. It is the largest single gain in the component chain (MAE 2.62 → 1.97, .843 → .872), larger than adding the comparative descriptor itself. This is consistent with the linear probing in Figure 10, where the probe AUROC increases from .798 to .843 as the comparative descriptor and within-image centering are added.
Q3.
The proposals are identical. ObjEmbed in Table 2 uses the same CountGD++ proposals, NMS and point matching as Pinpoint, and is trained on the same Real-ZAC training split. The only difference is the training recipe, as ObjEmbed is fine-tuned following its original recipe. The gain of Pinpoint over ObjEmbed therefore does not come from the proposals. To avoid confusion, we will state the shared proposals in Section 5.2
| Method (Proposals) | MAE ↓ | RMSE ↓ | ↑ |
|---|---|---|---|
| ObjEmbed (CountGD++) | 2.73 | 3.70 | .802 |
| ObjEmbed (WeDetect) | 3.26 | 5.27 | .708 |
| Pinpoint (CountGD++) | 2.09 | 3.29 | .872 |
| Pinpoint (WeDetect) | 2.47 | 4.85 | .815 |
We thank the reviewer for the thoughtful review and appreciate the positive assessment of the method’s practicality.
Q1.
While MuSc and Odd-One-Out both compare instances, Pinpoint differs in what the comparison is used for. It turns a within-image comparison into a per-instance intact/defective decision for a queried class on unseen classes, without any threshold. Neither prior method provides this capability, which rests on three design choices described below. We have cited and discussed Odd-One-Out in Section 2 of the revision.
(1) Training-free comparison. Odd-One-Out improves generalization through DINOv2 feature distillation, but its matching features, the attention over matched voxels and the anomaly decision are still learned on seen categories. Pinpoint instead computes the comparison by mutual scoring on frozen DINOv3 features without any learned parameters, so the comparison itself is not fitted to the training classes.
(2) Class-independent reference point. MuSc outputs raw distances whose scale varies with the class and the reference images, so it can rank instances but cannot classify them with a fixed rule. Within-image centering (Eq. 4) expresses each instance relative to its own image, so that zero means "typical for this image" in every class. This step yields the largest single gain in our ablation.
(3) Language-based decision. The comparison serves as a cue rather than as the decision itself. It is injected into a region token that also carries semantic information, and the intact/defective query margin (Eq. 8) makes the final decision. This restricts the decision to the queried class and provides a fixed rule that transfers to unseen classes.
The task and its benchmark. These design choices are driven by the requirements of a new task, which we introduce together with its benchmark. Zero-shot anomaly-aware counting asks a model to count the intact and defective instances of a queried component in a single real image, on classes never seen during training. No existing setting combines single-image input, per-instance defect state, counting output and a class-disjoint split. Real-ZAC supports this task with real industrial components, instance-level intact/defective labels, class-disjoint splits and a protocol that evaluates counting error and per-instance state jointly, whereas the ToysAD-8K and PartsAD-15K datasets of Odd-One-Out are synthetic. Pinpoint shows that the task is solvable and provides a reference point for future methods on this benchmark.