- Rating
- 3(+1)
- Confidence
- 2
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2(+1)
Read review
Paper summary
A training-free, test-time refinement layer for frozen feed-forward multi-view 3D predictions, driven only by RGB correspondences. Stage 1 jointly updates anchored cameras and a smooth depth field, with one bounded nuisance variable per unique matched source ray. Stage 2 fixes the fitted cameras, discards the nuisance, and refits the persistent depth field to the original correspondences. Evaluated across multiple frozen backbones and datasets against the unrefined prediction are done.
Critical strengths
Portable and architecture-agnostic. One fixed configuration is applied unchanged across several distinct backbones, requires no training.
Critical weaknesses
-
Comparison to prior work is too narrow to support the novelty of the method. Related work surveys a substantial line of directly relevant methods, but only one is actually run, and only on part of the data and metrics — the rest are cited, but not compared against. Without testing against the closest existing methods, it’s hard to tell whether the gains come from a genuinely new mechanism.
-
The relationship to that prior work is not clearly stated, which makes the paper’s own contribution hard to pin down. Several cited methods already combine a frozen/learned prediction with test-time, correspondence-driven correction — conceptually close to this paper’s core idea. The paper doesn’t explain what specifically differs from them, so a reader can’t tell which parts of the design are new versus inherited.
Questions for authors
1.With the temporary per-ray variables removed, the two optimization stages appear to share the same objective over the persistent depth field once the camera is fixed. How much of the two-stage design’s benefit holds independently of the per-ray mechanism, versus being attributable to that mechanism alone?
- The external baseline is evaluated only on camera accuracy and underperforms the unrefined prediction in most of those cases. Could the authors clarify why. Is this a genuine limitation of that method, or a difference in configuration between the two methods?