- Rating
- 2
- Confidence
- 4
- Informativeness
- 1
- Presentation
- 2
- Soundness
- 1
Read review
Paper summary
This paper introduce MAP2SLAM, that build a SLAM pipeline with existed components such as 3DFM, loop detection, iPGO, confidence-weighted 3D pointmap alignment and etc.
Critical strengths
The pipeline shows a good performance, but with existed compoments and overlapped scheduling from prior works.
Critical weaknesses
-
The introdution is not clear, the motivation does not vary much with the baselines.
-
The related work is fairly weak. Authors should introduce the baselines to motivate the contribution.
-
Most of the components utilized are introduced in prior works, the scheduling is also handcrafted and overlapped with existed systems, leaving the methodological novelty of the proposed framework unclear.
-
There is no clear evidence to show the improvement on mapping.
-
No speed and memory comparison.
Questions for authors
Addressing my concerns on clarity, novelty and experiments.
Response to Reviewer XY31
Thank you for your critical feedback. We take your concerns seriously and address each point below, with manuscript revisions marked in blue.
1. System design and motivation (W1, W2, W3)
Building a SLAM system around a 3DFM comes down to three questions:
① what to observe,② when to observe, and③ how to optimize. Although individual modules may look similar to existing ones at first glance, all three mechanisms are tightly and cleanly designed around a single frozen streaming 3DFM:① What to observe: Unlike pairwise two-view matching or chunk-based inference, we build on a frame-streaming 3DFM for continuous per-frame tracking in causal mode, while reusing cached encoder features in fresh bidirectional context to re-observe loop pairs and historical segments without re-encoding images.② When to observe: Without an external VPR model or external optical flow, the model's cached encoder tokens trigger loop closure and its predicted motion drives a commit-or-rollback KV probe for keyframe admission. Meanwhile, historical segment re-observations are scheduled into idle GPU intervals during online tracking, avoiding a large end-of-sequence backlog.③ How to optimize: Rather than optimizing only rigid poses or submaps, we optimize at the frame and dense-depth level: online pose graph optimization continuously corrects per-keyframe trajectory drift during tracking, and the resulting trajectory anchors dense map optimization to jointly refine keyframe poses and dense depth maps at sequence end.The table below compares how existing 3DFM pipelines and Map2SLAM address these three questions:
①3DFM Mode①Frame-wise②Loop Closure②No Ext. VPR②KF Gate②No Ext. Flow③Global Pose Opt.③Online Pose Opt.③Dense Map Opt.Following your suggestion, we have revised the Introduction to clarify this motivation and expanded Related Work to discuss the compared baselines.
2. Evaluation of dense reconstruction (W4)
The table below reports the mean 3D reconstruction metrics across the Oxford Spires sequences against LiDAR ground truth (added to Appendix A, Table 4). Even before dense refinement, Map2SLAM improves over LingBot-Map across all metrics, and dense refinement brings a further gain.
“w/o ref.” denotes the map before dense refinement.
3. Speed and memory comparison (W5)
The table below compares the end-to-end runtime and peak GPU memory of all methods on KITTI 05 (2,761 frames) on the same machine (added to Appendix C, Table 5).
With 2 GPUs, front-end tracking and back-end optimization run on separate GPUs; with 1 GPU, both run on the same GPU.
—indicates CPU-only execution, and † denotes evaluation on native keyframes only.