- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 1
Read review
Paper summary
This paper proposes CamoSplat, which modeling temporal appearance changes in driving-scene 3D Gaussian Splatting. It introduces three main components: MoTB models different appearance changes for each Gaussian. Morlet wavelet gating controls when and how strongly these changes happen. Sensor-specific opacity wavelets model different visibility changes for camera and LiDAR. Experiments on multi datasets show improvements in image and LiDAR reconstruction quality over existing methods.
Critical strengths
S1. MoTB combines shared temporal networks with per-Gaussian weights, allowing different temporal appearance patterns without separate networks for each Gaussian.
S2. Morlet wavelet gating and sensor-specific opacity provide flexible temporal control for camera and LiDAR rendering. The method achieves good results across multiple driving datasets.
Critical weaknesses
W1. The experiments show better overall reconstruction, but do not fully verify the claimed temporal accuracy.
- Better image quality does not mean accurate traffic-light switching. Fig. 4 illustrates one transition, but light-state accuracy and switching-time error across events are not reported. Thus, the claim of accurate event timing remains insufficiently validated.
- Fig. 3 compares Morlet and Fourier using dictionaries of the same size, but shows only two visual examples. Without quantitative results, it is unclear whether Morlet is consistently better.
- The 50% uniform split may still place test frames close to training frames. This alone does not support the claim that simple interpolation cannot recover temporal changes.
W2. The need for the two-part temporal design and its added cost is not sufficiently established.
- Table 3 shows that adding gating to MoTB improves results, but it also adds parameters. It is unclear whether the gain comes from the two-module design or from more parameters. A comparison with a single temporal module of similar size would help clarify this.
- Training time and peak memory are about 1.8× and 2.4× those of SplatAD, while rendering speed drops from 37.4 to 21.0 FPS. The cost of each module is not reported, and there is no comparison with simpler models under similar budgets. It is unclear whether a simpler model could achieve similar quality at lower cost.
Questions for authors
Q1. Table 2 reports Depth and CD in m, while SplatAD uses median squared depth error, which has units of m². Does this paper use a different metric, or is this a labeling error?
Q2. The authors manually select 10 scenes from each dataset. How can the authors ensure that this selection does not introduce bias?
Q3. For the 50% LINSPACE split, what is the actual time gap between training and test frames? How does this setting demonstrate that simple temporal interpolation is insufficient?