- Rating
- 2
- Confidence
- 4
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
GaussianDiffuser is a self-supervised pre-training framework for vision-centric 3D driving perception. It corrupts multi-view image latents using a flow-matching-style interpolation, lifts the corrupted features into continuous 3D Gaussians, refines them with timestep-conditioned AdaLN-Zero blocks, and rasterizes RGB, LiDAR depth, and feature predictions toward clean targets. During downstream fine-tuning, the noise scheduler and projection head are removed, is used, and probabilistic voxelization connects the representation to occupancy and detection heads. The method is evaluated on nuScenes/Occ3D, SurroundOcc, 3D detection, and AV2-to-nuScenes transfer; the controlled comparisons against a rendering-only GaussianFormer-2 baseline show improvements from 0.159 to 0.151 Abs Rel and from 35.58 to 36.56 Occ3D mIoU.
Critical strengths
-
The paper includes meaningful matched controls. Against the same GaussianFormer-2 pipeline, GaussianDiffuser improves depth, occupancy, corruption-domain transfer, and ImageNet-initialized performance.
-
The transfer evaluation is broad. The AV2-to-nuScenes zero-shot depth result is particularly promising, reducing Abs Rel from 0.626 for NeRP3D to 0.273.
Critical weaknesses
-
The headline gains overstate the controlled evidence. The abstract emphasizes a 17% Abs Rel reduction and +2.4 Occ3D mIoU using cross-paper comparisons, whereas the matched gains are approximately 5% Abs Rel and +0.98 mIoU. SurroundOcc also uses a different input resolution, and the detection comparison uses different downstream detectors across methods (Abstract, p. 1; Tables 3 and 5, pp. 8 and 13).
-
Key quantitative and implementation facts are internally inconsistent. If Table 11 is correct, GaussianDiffuser adds 112.84 GFLOPs, or 11.7%, rather than 0.39 GFLOPs; the claimed 49.2% reduction relative to NeRP3D would also be incorrect. The 37.9/36.8 mIoU discrepancy affects another headline result, while the clean-versus-corrupted feature paths remain under-specified (Section 4.4, p. 8; Figure 2 and Equation 3, pp. 4–5; Table 11 and Appendix C, p. 18).
Questions for authors
-
Please specify the complete information flow during pre-training: do the depth network, Gaussian initialization, Equation 3's , Gaussian colors/features, and projection head receive or ? Is stop-gradient, and is the ConvNeXt backbone updated (Figure 2 and Sections 3.1–3.3, pp. 3–6)?
-
What is the correct 17-class Occ3D result, 37.9 or 36.8 mIoU? Please explain the source of the discrepancy and confirm which value underlies the +3.8 and +2.4 comparisons (Table 2 and Section 4.4, p. 8).
-
Which computation figure is correct, 1079.05 or 966.60 GFLOPs? Please define the measurement boundary consistently; if 1079.05 is correct, the claims of +0.39 GFLOPs and negligible overhead should be revised (Table 11 and Appendix C, p. 18).