- Rating
- 3
- Confidence
- 2
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 3
Read review
Paper summary
This paper presents LeanSplat, an efficient Language Gaussian Splatting framework. It alternates semantic-opacity optimization with multi-view feature aggregation and prunes low-contribution Gaussians from the language branch. It further compresses language features using opacity-weighted K-means. At query time, text scores are computed on shared prototypes and directly rasterized into pixel-level score maps, avoiding high-dimensional feature reconstruction.
Critical strengths
-
The method combines semantic point pruning, shared feature prototypes, and direct score rendering to reduce language-branch storage and query costs.
-
On LERF, it removes 83.25% of language primitives and reduces language storage to 2.94 MiB per scene while achieving 65.5% mIoU. Query throughput exceeds 500 queries/s on an A100 GPU.
Critical weaknesses
1. Limited justification for optimizing only semantic opacity.
The method freezes Gaussian positions, scales, and rotations and optimizes only semantic opacity. While this preserves the pretrained RGB representation, it limits the ability to adapt Gaussian support to semantic boundaries. An ablation allowing language-specific geometric adjustments would clarify the accuracy–efficiency trade-off of this design. Why not optimize other Gaussian attributes?
2. The interpretation of semantic opacity as visibility requires stronger justification.
Why do the authors use semantic opacity for prototype clustering? The authors refer to this as “Visibility-guided prototype construction” but why use opacity rather than the alpha-blending weight, which reflects actual visibility?
3. Unclear ScanNet evaluation protocol after pruning.
Tables 2 and 3 evaluate pruned models only on retained points. Why does reducing the number of Gaussian primitives reduce the number of ScanNet points used for evaluation? Could the models before and after pruning be evaluated on the same full ScanNet point cloud? Please clarify how predictions are mapped to ScanNet annotation points and how the retained points are selected.
Questions for authors
Please refer to the weaknesses above.