- Rating
- 2
- Confidence
- 2
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
Main contribution: GeLoc3r adds Geometric Consistency Regularization (GCR) to ReLoc3r during training, while preserving direct relative pose regression at inference.
Method:
- Reconstruct 3D points from ground-truth depth and camera intrinsics, then project them into the other image using the predicted pose.
- Encourage agreement between MASt3R descriptors at the corresponding locations.
- Use FusionTransformer weights for weighted RANSAC sampling and enforce consistency between the regressed and solver-estimated poses.
Reported evidence:
- Training uses ten datasets; evaluation covers five relative pose benchmarks and two localization benchmarks unseen during training.
- Against ReLoc3r retrained on the same data, AUC@5° improves from 39.86 to 50.45 on MegaDepth1500 and from 34.20 to 41.42 on CO3Dv2.
- Both models are reported to run at 33 ms per image pair. The added geometric modules are used only during training.
Critical strengths
1. Improved accuracy without additional geometric computation at inference.
- Design: Depth, descriptor reprojection, and the geometric solver provide supervision only during training.
- Evidence: Figures 2–3 preserve the direct pose regression path. Table 1 reports the same runtime of 33 ms per image pair for both models.
- Significance: This preserves the practical benefit of fast pose regression while improving accuracy.
2. Consistent gains over the baseline retrained on the same data.
- Relative pose: Table 1 shows improvements at all three AUC thresholds across five benchmarks.
- Localization: On unseen 7-Scenes, the reported average rotation error improves from 1.12° to 1.03°, while position error remains 0.04 m at the reported precision. On unseen Cambridge, average position and rotation errors improve from 0.60 m / 0.61° to 0.51 m / 0.52° (Tables 2–3).
- Ablation: Table 4 shows gains when adding the descriptor loss and then the full configuration.
- Significance: The evidence supports the usefulness of the overall training configuration across multiple datasets and metrics.
Critical weaknesses
1. The main baseline comparison does not sufficiently establish the source and extent of the gains.
What is established:
- Table 1 compares GeLoc3r with a ReLoc3r baseline retrained on the same data. Some improvements over this baseline are substantial.
- Table 4 provides supporting evidence under a controlled, smaller setting: all variants use MASt3R initialization and 10,000 ScanNet training pairs, with AUC@5° increasing from 19.4 to 20.3 and then 22.4.
What remains unclear:
- For Table 1, the paper does not sufficiently specify whether the baseline and GeLoc3r share initialization, training budget, corresponding trainable modules, optimization settings, and model-selection criteria beyond the proposed GCR additions.
- The retrained baseline is substantially below the published ReLoc3r result on MegaDepth1500: 39.86 versus 49.6 AUC@5°, while GeLoc3r reaches 50.45. The cause of this gap is not explained.
- The original ReLoc3r uses DUSt3R initialization, whereas GeLoc3r uses MASt3R. The initialization of the main Table 1 baseline needs to be specified separately. ReLoc3r's own Table 8 demonstrates sensitivity to initialization on ScanNet1500, making this a concrete comparison concern rather than evidence of an implementation error.
- Table 4 supports the benefit of the overall additions, but does not resolve the main baseline's performance gap or isolate the effects of learned weighting and the prior.
Effect on my assessment: The published numbers come from different training conditions and do not invalidate the internal comparison. However, without a sufficiently specified and validated baseline, I cannot confidently determine how much of the main improvement is attributable to GCR or how substantial the advance is over an appropriately trained ReLoc3r model. This uncertainty is the primary reason for my weak rejection; I am not claiming that the baseline was trained incorrectly. Validation of the baseline and convincing gains under controlled conditions could change my recommendation. If the authors validate that the baseline is appropriately trained and evaluated, and demonstrate convincing improvements attributable to GCR under controlled conditions, I would be willing to revise my recommendation toward acceptance.
References: GeLoc3r Section 4.1 and Tables 1 and 4; ReLoc3r, arXiv:2412.08376v2, implementation details and Tables 8 and 11.
2. The construction and corrective effect of the solver supervision remain unclear.
What the paper describes:
- Section 3.5 defines descriptor pairs at the same subsampled grid index. How these pairs and their weights map to the PnP correspondences is not clearly explained.
- Figure 3's caption describes constructing 3D–2D correspondences by transforming and projecting depth-derived points using the current regressed pose.
- It does not specify a step that corrects those projected locations through image-based descriptor matching.
- Figure 3 labels the 3D points in the cam2 frame, leaving the coordinate convention for the PnP inputs unclear.
Why this matters:
- If source-frame points are paired with target coordinates and passed directly to PnP, then itself has zero reprojection error.
- Under this construction, changing sampling weights alone does not introduce an independent observation that corrects the pose.
- Table 4 shows improved final-model performance, but does not directly show that the solver output is closer to ground truth than its input.
Effect on my assessment: I cannot adequately assess the central supervision mechanism from the current description and evidence. This is a conditional concern about the documented construction; it does not establish that the implemented solver is ineffective.
References: Sections 3.5–3.6, Figure 3, Algorithm 1, Table 4.
Questions for authors
1. Validate the Table 1 baseline and clarify the attribution of the gains.
- Does the baseline use the original DUSt3R initialization or the MASt3R initialization used by GeLoc3r? Please specify all differences between the two models beyond GCR, including training budget, corresponding trainable modules, optimization settings, and model-selection criteria.
- What explains the baseline's lower MegaDepth1500 result relative to published ReLoc3r? If the original checkpoint has been evaluated with your pipeline, please report that result to help distinguish evaluation differences from retraining differences.
- What evidence establishes that the baseline is appropriately trained and that the gains persist when these conditions are controlled? This is central to whether I would reconsider my recommendation.
2. Define the correspondences used by PnP.
- Specify the coordinate frame of the 3D points and how target 2D coordinates are obtained.
- Section 3.5 defines descriptor pairs at the same subsampled grid index, whereas Figure 3 describes pose-projected coordinates. How do these descriptor pairs and their weights map to the 3D–2D correspondences passed to PnP?
- Are the target 2D coordinates those grid locations, projections under the predicted pose, or independently estimated image correspondences? If projections alone are used, what supplies a corrective signal beyond recovering the pose that generated them?
3. What evidence shows that the solver improves its input pose?
- Can you provide ground-truth rotation and translation-direction errors for and on the same training pairs, including the fraction improved and the magnitudes of improvement and degradation?
- This evidence would directly test the current claim that the solver provides more accurate supervision.
4. Clarify and isolate the changes in the ablation.
- Does the “+ Descriptor loss” variant in Table 4 also learn FusionTransformer weights? What exactly changes in the final row?
- If existing comparisons with uniform weighting or without the prior are available, please share them to clarify which components account for the gain.
- Appendix A.1 states that and were selected through ablation studies. What did those studies show?
5 comments
Q1b. What explains the baseline's lower MegaDepth1500 result relative to published ReLoc3R? If the original checkpoint has been evaluated with your pipeline, please report that result.
We evaluated the official ReLoc3R-512 checkpoint with our evaluation pipeline and reproduce the published results (MegaDepth1500: 49.6/67.9/81.2 AUC@5°/10°/20°; ScanNet1500: 34.79/58.37/75.56; RealEstate10K: 66.70/80.20/88.39). The gap therefore comes from our retraining, not from evaluation differences.
Our retraining differs from the official recipe in three respects:
- Initialization. We use MASt3R instead of DUSt3R because GCR requires compatible MASt3R descriptor heads. ReLoc3R's own Table 8 shows that this change alone lowers ScanNet1500 AUC@5° from 34.79 to 32.62. Our baseline (33.57) is consistent with that figure.
- Training data composition and scale. Official ReLoc3R is trained on about 8M pairs from seven datasets: CO3Dv2, ScanNet++, ARKitScenes, BlendedMVS, MegaDepth (about 1.8M pairs), DL3DV (about 1.1M pairs) and RealEstate10K. Our 10-dataset mixture shares six of them and, in place of DL3DV, adds StaticThings3D, Waymo Open, WildRGB-D and Habitat. We do not use DL3DV, and the official repository notes that its released training setup is “not strictly equivalent to what was used to train Reloc3r,” so the official mixture cannot be reproduced exactly. Both recipes sample 50K pairs from each dataset per epoch, so MegaDepth makes up one tenth of each of our epochs, against one seventh in the official mixture, which plausibly matters most for MegaDepth1500's large viewpoint and intrinsics variations.
- Training budget. The official ReLoc3R script trains for 100 epochs with 5 warm-up epochs, a learning rate of decaying to , a frozen encoder, and 50K pairs per dataset per epoch. GeLoc3r and our retrained baseline each train for 100 epochs with 10 pairs per GPU on eight L40S GPUs (80 pairs per batch across GPUs). The released script uses 32 pairs per GPU on eight H800 GPUs (256 pairs per batch across GPUs). The official paper reports a batch size of 8 on eight AMD MI250x-40G GPUs, and the repository states that the released script is “not strictly equivalent to what was used to train Reloc3r”. We therefore cannot match the official budget exactly.
The gap to the released model therefore reflects the differences in training recipe listed above, not the evaluation. Our retrained baseline is trained under the settings listed in Q1a and serves as the reference for Table 1. The evidence that the gains persist under controlled conditions is given in Q1c.
Q1c. What evidence establishes that the baseline is appropriately trained and that the gains persist when these conditions are controlled? This is central to whether I would reconsider my recommendation.
We address the two parts in turn.
(a) The baseline is appropriately trained.
- Evaluation is validated. Our pipeline reproduces the published results of the official ReLoc3R-512 checkpoint, so any baseline gap reflects training, not evaluation.
- Matched training budget. Both models train for 100 epochs with the same data sampling and batch size, as specified in Q1a and Appendix A.2.
- Low run-to-run variance. All results are averaged over three runs. The standard deviation of AUC@5° is ±0.1 for the baseline and ±0.12 for GeLoc3r, well below the reported gains (e.g., +10.6 on MegaDepth1500).
(b) The gains persist under controlled conditions.
- Controlled comparison at full scale (Table 1). Table 1 compares GeLoc3r with the retrained baseline under the settings listed in Q1a. GeLoc3r improves on all five relative-pose benchmarks and both localization benchmarks.
- Small-scale ablation (Table 4). On ScanNet1500, the pose-only, descriptor-loss, and full variants achieved 19.4, 20.3, and 22.4 AUC@5°, respectively.
Q2. Correspondences used by PnP
We thank the reviewer for pointing out this ambiguity. Figure 3 and Section 3.5 of the revised paper explain how the correspondences passed to PnP are constructed.
(1) Coordinate frame and 2D targets
- 3D points. For each matched pixel in , we unproject its ground-truth depth with intrinsics to obtain in the camera-1 frame.
- 2D targets. We obtain in using MASt3R's fast reciprocal matching (Leroy et al., 2025, Sec. 3.3) on the dense descriptor maps from the frozen MASt3R heads. A match is a pair of pixels that are mutual nearest neighbors in descriptor space.
We thank the reviewer for the careful reading and the constructive questions. We answer each question in turn.
Q1. Validity of the Table 1 baseline and attribution of the gains
Q1a. Does the baseline use the original DUSt3R initialization or the MASt3R initialization used by GeLoc3r? Please specify all differences between the two models beyond GCR, including training budget, corresponding trainable modules, optimization settings, and model-selection criteria.
The Table 1 baseline uses the same MASt3R 512-DPT initialization as GeLoc3r, not the original DUSt3R initialization. We chose MASt3R because GCR relies on MASt3R's descriptor heads, which must be compatible with the backbone features. To keep the comparison controlled, the baseline uses the same initialization.
Apart from the GCR components, the two models use the same training configuration:
Using three evaluation datasets same as the official reloc3r evaluation protocol, we evaluated both models after each epoch on 1,000 pairs each from ScanNet1500, the ARKitScenes test split, and the MegaDepth test split. For each model, we selected the checkpoint that achieved the lowest median evaluation loss on any of the three datasets. ScanNet1500 was used for both checkpoint selection and final benchmark evaluation.
The FusionTransformer, the descriptor heads and weighted RANSAC are used only during training, so the two models are architecturally identical at test time.