- Rating
- 1
- Confidence
- 4
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 3
Read review
Paper summary
ControlGS decomposes continual Gaussian splatting into attribute update control, structure update control, and historical recovery. It combines change-dependent parameter permissions, evidence-guided topology edits, and persistent-ID-based history records to update evolving scenes while preserving unchanged content and earlier states.
Critical strengths
The separation of attribute, topology, and history management is practically motivated. The framework also addresses concrete implementation issues, including Adam-induced drift in frozen parameters and historical recovery after Gaussian reordering, with focused checks targeting these failure modes.
Critical weaknesses
-
The main experiments do not validate the proposed controls. Section 4 states that the ten-scene experiments open all Gaussian attributes and use standard 3DGS growth, rather than the proposed attribute restrictions and structure-update policy. Table 3 also allows different update paths across rows, preventing meaningful attribution of improvements to either module. The focused checks in Table 5 verify specific implementation behaviors but do not resolve this experimental gap.
-
The methodological advance is insufficiently established. GaussianUpdate already separates appearance and geometric updates, while CL-Splats supports local optimization and historical recovery. The additional benefits of ControlGS’s permissions, heuristic scores, and persistent-ID bookkeeping are not convincingly isolated. Key event scores and uncertainty estimates are insufficiently specified, and historical recovery is not adequately tested over long sequences of mixed structural edits.
-
Figure 1 does not clearly communicate M1’s behavior. The four change categories are labeled, but their visual outcomes are difficult to distinguish. The figure does not show which attributes are updated or frozen, or how the resulting updates differ across categories. Explicit before-and-after examples and attribute-level annotations would make it more informative. “Orign” should also be corrected to “Origin.”
Questions for authors
- Why does the main evaluation bypass the proposed M1/M2 policies, and which components actually produce the reported gains? 2.What substantive capability does ControlGS add beyond GaussianUpdate’s staged updates and CL-Splats’ local optimization and history recovery?
- Could you provide matched-protocol ablations enabling M1 and M2 individually and jointly, with explicit update-path logs?
- Could you evaluate long sequences of additions, removals, splits, and merges, reporting state-recovery accuracy, total history storage, and recovery latency?