- Rating
- 1
- Confidence
- 3
- Informativeness
- 1
- Presentation
- 2
- Soundness
- 1
Read review
Paper summary
The submission proposes "Necromantic Gaussian," a continuous Level-of-Detail (LoD) framework built on top of Octree-GS. The method formulates runtime primitive simplification as a learned retention confidence ordering. An anchor-level router MLP takes base features and learned side features to predict a retention logit and slot-wise scale compensation. To address the gradient vanishing problem in hard primitive selection, the authors introduce a zero-opacity analytic backward pass where rejected primitives receive local alpha-compositing gradients without contributing to the forward rendered image. Additionally, a direct decoded-Gaussian count loss calibrates the confidence distribution against a requested workload budget. A single trained model is evaluated across continuous budget fractions (100%, 50%, 25%) on Mip-NeRF 360, Tanks&Temples, MatrixCity, and vanilla 3DGS.
Critical strengths
S1: Formulating continuous LoD through a unified, learned confidence ordering that supports runtime budget slicing without retraining or multi-checkpoint storage addresses an important deployment challenge in explicit radiance field rendering. S2: The conceptual decomposition between reconstruction feedback (determining which primitives preserve visual fidelity) and the straight-through decoded count penalty (controlling how many total primitives are admitted) offers a structured and theoretically clean perspective on budget-constrained primitive pruning.
Critical weaknesses
W1: The central methodological premise is empirically contradicted by the ablation study in Table 2. The primary technical selling point of this paper is the zero-opacity analytic backward pass (the "necromantic" gradient recovery mechanism), designed to prevent rejected primitives from getting trapped in non-recoverable deadlocks. However, Table 2 reveals that disabling this mechanism ("No analytic backward") leads to negligible differences on Mip-NeRF 360 (-0.055 dB at 50% budget, -0.101 dB at 25% budget) and actually improves PSNR on Tanks&Temples by +0.055 dB at 50% budget and +0.044 dB at 25% budget. Furthermore, removing the scale compensation module at 25% budget increases PSNR on Mip-NeRF 360 by +0.095 dB and on Tanks&Temples by +0.028 dB; removing warmup at 25% budget similarly yields performance increases (+0.022 dB and +0.014 dB). When core components exhibit negative or marginal contributions in realistic multi-view reconstructions, the claim that they are necessary to resolve pruning deadlocks collapses.
W2: Disconnect between Gaussian reduction and real-world rendering throughput in Table 5. The fundamental motivation of an LoD framework is to translate primitive reduction into substantial inference acceleration. In Table 5 on Mip-NeRF 360, reducing the budget from to cuts the active Gaussian count from 437k to 112k—a 74.2% reduction in primitives. Yet, the rendering speed only scales from 299.73 FPS to 352.91 FPS—a meager 17.7% gain. The authors do not provide a profiling breakdown to explain why cutting nearly three-quarters of the primitive workload yields such marginal runtime benefits, suggesting that per-anchor confidence computation, dynamic sorting, and threshold masking introduce substantial pipeline overhead that negates rasterization gains.
W3: Performance degradation over the underlying base model and inferior performance against existing baselines in Table 1. At 100% full capacity (), the proposed model achieves 27.709 dB on Mip-NeRF 360, underperforming its own foundational base architecture (Octree-GS achieves 28.019 dB). This indicates that the joint training of the router and side features penalizes the capacity of the base representation. At restricted budgets (50% and 25%), Matryoshka-GS outperforms the proposed method by 1.0 to 1.5 dB across both Mip-NeRF 360 and Tanks&Temples. The justification provided in the text regarding differing primitive counts does not alter the fact that the proposed approach delivers an inferior rate-distortion Pareto frontier.
W4: Unsubstantiated claims regarding generalization and representation independence in Tables 4 and 6. The authors claim in Section 4.5 that their method scales to large urban scenes (MatrixCity, Table 4) and in Section 4.7 that it is representation-agnostic (Vanilla 3DGS, Table 6). However, both tables solely report isolated metrics of the proposed method across scales () with absolutely zero baseline comparisons. Without comparing MatrixCity results against native Octree-GS or CityGS, or comparing Vanilla 3DGS results against standard opacity/scale pruning or random dropout baselines, these tables offer no comparative scientific value.
W5: Deficient manuscript polish and careless preparation. The paper contains blatant uncompiled syntax errors in the main text; specifically, on line 047 in the Introduction, an unresolved citation appears as ... (Ren et al., 2024; Kerbl et al., 2024; Fan et al., 2024; Liu et al., 2025; ? ; Guo et al., 2026). Additionally, the qualitative comparisons in Figure 4 contain low-resolution crops without magnified insets or difference error maps, making visual verification impossible. The submission metadata (e.g., the informal TL;DR "a type of lod(level of detail) for gaussian splatting") further reflects rushed preparation and a lack of academic rigor.
Questions for authors
Q1: In Table 2, why does removing the zero-opacity analytic backward pass improve PSNR on Tanks&Temples (+0.055 dB at 50% and +0.044 dB at 25%), and why does removing scale compensation yield a +0.095 dB boost on Mip-NeRF 360 at 25%? How do the authors reconcile these empirical results with the claim that these components are indispensable for recovering from bad pruning decisions and preserving coverage?
Q2: What is the detailed runtime profile of Table 5? Specifically, what fraction of latency is consumed by anchor router forward passes, confidence evaluation, and filtering, versus the CUDA rasterization stage? Why does a 74.2% drop in rendered Gaussians result in only a 17.7% FPS improvement?
Q3: Why are Tables 4 and 6 reported without baseline methods? What are the quantitative PSNR/SSIM/LPIPS numbers of standard Octree-GS on MatrixCity and simple opacity/magnitude thresholding on Vanilla 3DGS under identical Gaussian budgets?
Q4: Given that the proposed model incurs an initial quality drop at full capacity compared to base Octree-GS (27.709 dB vs. 28.019 dB on Mip-NeRF 360), what specific regularization or optimization dynamics cause the base field to degrade during joint routing supervision?