- Rating
- 2
- Confidence
- 4
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 3
Read review
Paper summary
AllocSplat selects 3D anchors using explicit geometry and appearance, then adjusts local offset and scale bounds using anchor spacing. It re-decodes Gaussian groups when the budget changes. DL3DV-140 and transfer experiments evaluate quality versus primitive count, with ablations of selection, scale adaptation, and re-decoding.
Critical strengths
-
The connection between spatial allocation and budget-dependent decoding is well motivated. The method changes not just which primitives are retained but how the retained support is represented at the requested budget.
-
The component studies address relevant confounders. Table 3 separates retaining previously decoded groups, re-decoding at frozen scales, and updating the scales. Selection and scale-rule variants are trained separately, and matched-count comparisons with ZipSplat are provided.
-
The evaluation takes care over common inputs, target cameras, and non-input target views. The cross-dataset results provide evidence beyond a single benchmark. The paper also reports limitations, including cases where smaller Gaussian groups are more efficient at matched counts.
Critical weaknesses
-
Independence from backbone pre-training is unresolved. Section 4.1 and Appendix A.1 state that DA3-Giant-1.1 was trained on DL3DV but do not establish exclusion of the 140 test scenes. Excluding them from AllocSplat training alone is insufficient. This is uncertainty, not evidence of leakage, but it limits claims about unseen-scene generalization.
-
Allocation gains need separating from system-level gains. External baselines differ in backbone and training. At 1024 anchors, the joint selector gains about 0.14 dB over spatial FPS without achieving the best LPIPS, while its low-budget advantage is larger. The conclusions should reflect this budget dependence.
Questions for authors
-
Can existing training records establish whether DL3DV-140 was excluded? If not, which existing evaluation scenes are demonstrably unseen by the backbone? Retraining the backbone is not requested.
-
Please summarize selection, scale adaptation, and re-decoding gains at low and default budgets using existing ablations, including the default-budget PSNR/LPIPS trade-off.
-
Can you provide a focused matched-device latency/memory comparison with the main budget-adaptive baseline, using the same number of target renders and stating whether the full geometry backbone is included?
P.S. I encourage the authors to address these questions carefully. I would be willing to raise my score if the responses adequately resolve my concerns.