- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
LonGaussian is a streaming feed-forward framework for reconstructing compact, renderable 3D Gaussian scenes from long image sequences with known intrinsics and unknown camera poses. It builds on a frozen LoGeR backbone for geometry and long-context features, predicts dense pixel-aligned Gaussians, and uses tracks from frozen AllTracker to guide a learned within-chunk merger. Rendered-depth filtering and a far-field Gaussian shell address additional cross-chunk and sky artifacts. Experiments on held-out DL3DV and RealEstate10K sequences compare rendering quality and Gaussian count at 64, 96, and 128 context frames. A separate single-scene study examines construction scalability and local rendering quality up to 3,768 input frames.
Critical strengths
-
An important problem addressed through a well-motivated design. The paper addresses both the memory cost of processing long sequences and the redundant scene representations produced by accumulating pixel-aligned Gaussians. Using multi-frame tracks to identify repeated observations provides a clear rationale for consolidation. The overall presentation is clear, and the distinction between streaming geometry estimation and Gaussian scene construction makes the approach easy to follow.
-
Impressive rendering-quality and compactness results against the evaluated streaming baselines. At 128 context frames on DL3DV, LonGaussian achieves 18.31 dB PSNR with 4.80 million Gaussians, compared with 14.83 dB and 13.67 million for OF3GS. On RealEstate10K, the corresponding results are 18.23 dB and 2.15 million versus 16.19 dB and 11.37 million. These are substantial gains in both quality and representation size. The component ablations also provide useful evidence that learned consolidation and artifact handling contribute to the final results.
Critical weaknesses
-
The dependence on the two frozen foundation models is insufficiently quantified. LoGeR supplies the point maps, camera poses, and cross-chunk alignment underlying Gaussian prediction, while AllTracker determines which observations can be consolidated. Consequently, geometry errors, track coverage, and track fragmentation can affect both rendering quality and the number of retained Gaussians. The paper acknowledges these limitations in Section 5 and Appendix E, and Figure 8 illustrates severe global-rendering artifacts associated with long-range misalignment. However, the component ablations in Table 3 do not measure how the accuracy of LoGeR's predictions or the density and reliability of AllTracker's tracks affect the final quality-compactness trade-off. This is particularly relevant because the evaluation uses method-specific predicted target poses, so image metrics reflect pose-estimation error as well as scene quality (Appendix D.3). A more direct analysis of these dependencies is needed to establish when the proposed consolidation remains effective and where the frozen priors become the main bottleneck.
-
The comparison and generalization evidence do not yet fully support the intended long-sequence setting. AnySplat and WorldMirror are included in Table 1, but every entry is OOM under the 24-GB memory budget. This establishes a useful resource limitation under the chosen setting, but leaves their rendering quality and Gaussian compactness unassessed. Both methods have reported feed-forward results with 200 input views on MatrixCity under their respective evaluation settings (AnySplat, Table 2; WorldMirror, Appendix B.4 and Table 10). A complementary comparison under feasible native inference settings, with the memory budget and other settings explicitly reported, would clarify the trade-off against these relevant offline methods.
The systematic multi-scene evaluation is also restricted to held-out sequences from DL3DV and RealEstate10K, both of which are used during training or adaptation, and to at most 128 context frames. The train/test separation is documented; the remaining concern is generalization to different domains and substantially longer sequences. The fixed sampling protocol in Appendix D.1 does not establish robustness to different input-view intervals or reduced overlap, which directly affect tracking and consolidation. The additional 3,768-frame study is valuable, but covers only one scene and evaluates quality using seven neighboring chunks rather than the complete accumulated representation. As the authors acknowledge, this reduces interference from distant misregistered chunks and does not establish full-scene global rendering fidelity. Multi-scene evaluation at greater lengths and on out-of-domain data, for example suitable sequences from MatrixCity or ScanNet++, would materially strengthen the central claim.
Questions for authors
-
Dependence on frozen priors. How do LoGeR's geometry and pose errors correlate with final rendering quality, and how do AllTracker's track density, coverage, and reliability affect Gaussian count and rendering quality? Can controlled measurements separate these effects from those of the learned merger, including separating target-pose error from scene-rendering error where feasible?
-
Offline baseline comparison. Can AnySplat and WorldMirror be evaluated under feasible native inference settings, such as shorter sequences or a larger explicitly stated memory budget, while retaining the current 24-GB comparison? Rendering metrics and Gaussian counts would help assess the quality-efficiency trade-off beyond whether inference fits in memory.
-
Long-sequence and domain generalization. What evidence is available for different input-view sampling intervals and for longer sequences across multiple unseen-domain scenes, such as MatrixCity or ScanNet++? In those experiments, can full-scene rendering quality be reported separately from local-chunk rendering to show how global consistency changes with sequence length?