- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
GAD-Splat addresses transient-object removal in 3D Gaussian Splatting (3DGS) reconstructions of casually captured scenes. The core observation is that accurate masking alone is insufficient: when surfaces behind distractors are observed in few views, photometric optimization over remaining pixels can settle on geometries that fit colors but misrepresent static surfaces, and joint geometry/appearance optimization corrupts the cross-view correspondences needed to supervise masked regions. The paper proposes a three-stage pipeline with masks fixed throughout. Validation spans six NeRF On-the-go scenes and nine self-captured scenes, reporting best mean PSNR/SSIM (23.68 dB / 0.836 on NeRF On-the-go) and strong LPIPS, plus ablations isolating each stage and qualitative RGB/depth comparisons.
Critical strengths
The key contribution, explicitly decoupling geometry from appearance optimization so that cross-view correspondences used for masked-region supervision remain fixed, is well motivated and directly supported by the ablations. The empirical evaluation is broad and the margins are consistent, not isolated to a single scene or metric. GAD-Splat is best on mean PSNR/SSIM in every occlusion group on NeRF On-the-go and on all three means for self-captured data, with per-scene tables showing it leads all metrics in several self-captured scenes even where DeSplat wins others.
Critical weaknesses
(1) The method's dependence on external, largely off-the-shelf components (GeoMotion motion priors, DINOv3 features, SAM2 whole-mask candidates, Depth Anything 3, TSDF fusion) is heavy, yet the paper provides no cost, runtime, memory, or sensitivity analysis for these dependencies. This is consequential because the pipeline's practicality and reproducibility are unclear: TSDF fusion plus dense depth prediction at training-view resolution plus SAM2 prompting is plausibly a significant overhead relative to baseline 3DGS training, and the paper's own limitations section concedes failures under insufficient unmasked observations or erroneous fixed geometry, which are precisely the regimes where the external priors would be most stressed.
(2) The quantitative ablation compares only configurations with/without CDR and CAT (Table 3); it does not isolate a "masks only, no geometry/appearance decoupling" baseline against which the decoupling principle itself is tested, nor does it report geometry-specific metrics that would substantiate the claim that geometry is actually better rather than merely producing better renders. Since the fixed-geometry assumption is the paper's core assumption, the absence of direct geometric evaluation weakens the central argument.
Questions for authors
(1) What is the memory overhead of the full pipeline (motion prior, DINOv3 features, SAM2 prompting/selection, Depth Anything 3 inference, TSDF construction and raycasting) relative to baseline 3DGS training, and how does it scale with the number of views?
(2) How sensitive are results to the external priors, e.g., what happens if GeoMotion or Depth Anything 3 fails or is replaced by a weaker model? Is there an ablation of motion-prior quality or depth-prediction quality?
(3) Can you report a geometry-specific metric (e.g., rendered-depth error against held-out reference depths, or surface accuracy against TSDF/LiDAR where available) comparing CDR against a masks-only baseline, to directly support the claim that decoupling improves geometry rather than only appearance?
(4) For the constrained appearance update, how much does the gradient projection matter versus simply applying the auxiliary losses with tuned weights? An ablation removing the projection (unconstrained auxiliary gradients, zero-order SH only) would clarify whether the constraint or the SH restriction drives the gains.
(5) The limitations note failures when a background surface is hidden in all source views. What fraction of masked pixels typically lack valid source observations in your datasets (the ρ_t = 0 case), and how does CAT behave in those regions, does it default to the rendering average?
Thanks for the efforts. I carefully reviewed all the comments and authors' responses. I think the key contributions are still limited and not fully validated, so I will keep my score.