- Rating
- 2
- Confidence
- 4
- Informativeness
- 2
- Presentation
- 1
- Soundness
- 2
Read review
Paper summary
The paper proposes a three-stage pipeline to reduce the number of Gaussians in a 3DGS scene with limited quality loss. Stage I establishes residual demand, Stage II builds per-Gaussian, per-view features and compresses them using projection to give credit to Gaussians whose rendering is not already covered by their neighbours, Stage III finally merges the Gaussians per block into fewer Gaussians by matching means and covariances. The paper reports roughly 9 to 12 times fewer Gaussians than vanilla 3DGS with short training times and comparable image quality on Mip-NeRF 360, Tanks & Temples, Deep Blending and Waymo.
Critical strengths
- According to the reported results, the method reaches roughly 9 to 12 times fewer Gaussians than 3DGS with roughly comparable image quality.
- The insight to only keep Gaussians whose rendering is not covered by neighbors is a good improvements over the common per-Gaussian importance scores.
- The choice of datasets is good and the reported metrics are relevant: per-scene results, peak memory, rendering speed, several hyperparameter sweeps.
Critical weaknesses
-
The method is very difficult to follow. Even for a reader familiar with the area, the methodology, and Stage II in particular, is very hard to follow. Steps are introduced without explaining what they do or why they are needed, the same notation are used for multiple meanings, and many symbols and terms are never defined. The authors should fix this and report the intuition and reasoning behind each design decision rather than only listing the steps and the math to improve readability. Specific examples:
- Introduction example. The example with responses (1,0),(1,0) versus (1,0),(0,1) relies on "responses" and "rows" before either is defined. It only becomes understandable after Section 3.4.
- h(t) = min{8, log(1 + t/a_t)}. This appears to be a log compression with a cap, presumably to stop large values from dominating, but no reason is given. The scale a_t is never defined, and it determines where each feature saturates. Is it a constant, a per-scene statistic or per-view? What is its value for each of the three features it is applied to?
- Per-camera projections (Eq. 4). D_v and N_RMS are not defined. It is unclear whether N_RMS normalizes each vector or each coordinate across Gaussians. Proposition 2 holds only in expectation and before the final normalization, and the error at d = 24 is not discussed. It is also not argued why the 100-dimensional per-view descriptor needs to be compressed, since it seems affordable, and no comparison against using it directly is shown.
- Other undefined symbols and terms. Ω_v and u_i^v in Eq. 2, the "flagged rasterization", how c_i is accumulated, "demand interface", "response coverage" (used before Eq. 9 defines it), "candidate set", "renderer support", "span novelty", "caps" and "seeded subset" in Appendix B.4, and "the archived demand/reduction base" in Section 4.2.2.
- Overloaded notation. Many symbols carry several meanings, for example:
- s_i is both the sketch in Eq. 4 and the allocation score in Eq. 12.
- a is the alpha support a_i^v, the scale a_t, the block median mass a_B, and a row label in Figure 1. It is also easily confused with opacity α_i.
- x is the per-view feature vector and, inside that same vector, the image x-coordinate.
- e_i is the demand count in Eq. 2 and a unit vector in Proposition 1.
- ℓ is the leverage score in Eq. 8 and the luminance in Eq. 21.
- N / 𝒩 denotes the number of Gaussians, min-max normalization, the normal distribution 𝒩(0, 1/d) on the same page, RMS normalization and a Gaussian density.
- Figure 1. The figure is unclear and uses terminology that is not used or defined in the text: "distinct response", "response energy", "Redundancy Mixture" and the High/Low priority scale. The meaning of the a/b/c rows and the check mark in Stage II-B is not explained, nor is "absorbed sources". The figure shows at least 24 views ("view 24") while the method samples 10 cameras.
-
The central contribution is not shown to matter. The paper spends most of its explanation on Stage II, but its own ablations show almost no effect on quality: Demand-only allocation (β = 0, Table 8): PSNR: 28.87; #GS: 0.29M Full method (β = 0.25): PSNR: 28.88; #GS: 0.26M The full method reaches the same quality with about 10% fewer Gaussians, but because quality and count change together and no variance is reported, it is not possible to tell whether this difference is real. Can you compare scoring rules at the same final Gaussian count? Given how close the results are, we would also recommend reporting results using multiple seeds with standard deviation. A quality-versus-count curve over several budgets would be even more informative.
-
Why should residual demand guide compression? Stage I counts pixels with high reconstruction error around each Gaussian. This is a known heuristic for densification, where it makes sense: high error indicates that more capacity is needed. It is much less clear to us why it should decide how much capacity each region keeps during compression. A residual measures how well the current Gaussians fit the training images, not whether they are redundant. A region with low error and one thin Gaussian per structure can be irreplaceable yet receive a small budget, while a high-error region crowded with badly placed Gaussians is protected. Table 8 shows that demand alone (β = 0) performs as well as the full method, so this unexplained heuristic carries most of the allocation. Please justify this choice.
-
The Stage II features are not ablated. The ten-dimensional per-view feature in Eq. 3 combines visibility, alpha support, demand, footprint, image position, depth and colour, but the paper never shows what each contributes. Table 5 only replaces the whole feature set with Gaussian parameters. Please report leave-one-group-out results or results where you only use the specific feature.
-
Evaluation of the work.
- Scene subset: Mip-NeRF 360 is evaluated on 7 of its 9 scenes. Most baselines report all nine in their own papers, so the numbers cannot be compared with the literature. Please report the full benchmark.
- Variance.: No result reports seeds or variance. Several of the differences discussed in the text are 0.02 to 0.08 dB, which is within typical run-to-run variation for 3DGS.
-
Minor issues
- Typo: "creadit" in the contributions list.
- The method samples only 10 training cameras (Table 7), and this choice is not justified or tested. Mip-NeRF 360 scenes have 150 to 300 images, and Waymo sequences are much more spread out. It might be that we misunderstand the contents of this table though, so additional explanation would be nice.
Using leverage scores to account for redundancy among neighbouring Gaussians is a sensible idea, and the reported reduction in Gaussian count is substantial. However, the paper's own ablations do not show that the claimed central contribution, Stage II, has a significant effect. Most of the allocation is carried by an error heuristic whose role in compression is not explained. The evaluation uses a non-standard scene subset. The methodology is very difficult to follow. A fixed-count comparison with seeds, a complete description of the pipeline, the full benchmark and a substantially clearer presentation would be needed for acceptance.
Questions for authors
The quality of the splat reduction could be better assessed if the authors provided the full scenes as supplementary material. I don't have specific additional questions for the authors. I have detailed the clarifications that are needed above to improve the quality of the work.