- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
F²SLAM integrates high-frequency DROID-style tracking and low-frequency Flow3r predictions within a shared dense bundle-adjustment framework. The high-frequency branch updates tracking correspondences, while the low-frequency branch selectively replaces them after consistency checks and provides geometry for initialization. Experiments demonstrate competitive trajectory estimation and dense reconstruction.
Critical strengths
-
Practical integration. Expressing both branches’ outputs as correspondence targets and weights provides a practical way to incorporate multi-view information into an existing dense BA pipeline.
-
Competitive results. The system achieves strong trajectory estimation in the uncalibrated setting, particularly on TUM and Replica, and improves reconstruction completeness on 7-Scenes.
Critical weaknesses
-
The independent contribution of measurement refresh is insufficiently established. On Replica, basic tracking already achieves a strong ATE of 0.0027 m, leaving relatively modest gains from measurement refresh (0.0026 m) and the full system (0.0023 m). It would be helpful to see ablations on other datasets to better understand how much measurement refresh adds beyond the already strong tracker, initialization, and intrinsic refinement.
-
The benefit of measurement locking remains unclear, as the ablations do not separate its contribution from correspondence replacement itself.
Questions for authors
-
Could the authors extend the ablations to TUM and KITTI, keeping intrinsic optimization and other backend settings identical? Given the strong performance of Basic Tracking on Replica, these comparisons would help clarify the additional benefit of measurement refresh.
-
What is the empirical benefit of locking accepted measurements against subsequent high-frequency updates? A comparison with replacement without locking would help establish its contribution. Jointly retaining both measurement sources could provide another informative comparison.
-
Could the authors report the runtime and peak GPU memory usage of Basic Tracking, the initialization-only variant, and the full system under identical settings? This would help clarify the accuracy–efficiency trade-off introduced by measurement refresh.
-
Could the authors revisit the layout of Figure 2? The “Persistent Dense Factor Graph” block in particular appears crowded and is difficult to parse, while there is noticeable unused space on the right. Adjusting the layout would greatly improve readability.