- Rating
- 2
- Confidence
- 2
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
The paper presents KB-Splatting, a differentiable reconstruction method for sparse-view CBCT. Its main design choice is to replace Gaussian primitives with anisotropic generalized Kaiser-Bessel kernels: compactly supported, with kernel extent and profile sharpness exposed as separate parameters, which the authors motivate by the sharp attenuation edges typical of CT. Since the kernels admit an analytic cone-beam projection, the model is optimised against measured projections rather than a surrogate. Primitives are inserted and relocated according to the local reconstruction error. The submission also introduces a paired CBCT dataset with real projections from two scanners, and reports a mean gain of 0.93 dB in attenuation PSNR over state-of-the-art methods, with training roughly 2× faster.
Critical strengths
The choice of basis is well argued. Kaiser-Bessel kernels are compactly supported and have a closed-form X-ray transform, and the authors expose support width and profile sharpness as two independent parameters — at the sharp attenuation edges of CT that is the relevant degree of freedom, and it is what a Gaussian cannot give, since a single σ fixes both at once. Because the substitution happens inside an otherwise unchanged 3DGS pipeline, other splatting-based CT methods should be able to take it up without re-deriving their optimiser.
The paired dataset may turn out to be the most reusable part of the submission. Two systems contribute measured projections together with reference volumes, so the evaluation runs on real acquisition; synthetic DRRs, as the authors point out, carry neither scatter nor calibration error.
The reported numbers are 0.93 dB PSNR and roughly 2× faster training. If those hold under a matched tuning budget, this is accuracy that is not being paid for in compute — a combination rarer than it should be.
Critical weaknesses
The quantitative evidence is thin. Everything in the paper comes from 15 scans on two scanners, and only as averages — no per-scanner breakdown, no spread across repeats. Fig. 4 does not carry the aggregate either: on the neck case R²-Gaussian is ahead (44.54 vs. 43.34 dB). A 0.93 dB mean over 15 cases would be a good deal more convincing with a per-case table and some estimate of variance.
Calling the setting sparse-view is a stretch. The sparsest configuration still uses about 150 projections (the other two use roughly 300 and 600), and going from 600 down to 150 costs KB-Splatting only 0.24 dB. That curve is essentially flat, which suggests the experiments never enter the ill-posed regime the paper is motivated by. Results in the few-dozen-views range are what this claim needs.
The ablation does not isolate the proposed primitive. In the controlled comparison of Table 2, KB kernels improve on a matched Gaussian by 0.04–0.12 dB and run 8% faster; the headline numbers in Table 1 are 0.93 dB and about 2× over R²-Gaussian. The gap between those two settings is the issue: most of the improvement would then have to come from population control, initialisation or implementation detail rather than from the basis itself — which is the paper's central claim.
Two things around the baselines and the reference volumes need a direct answer. The neural baselines land near 15 dB, some 30 dB below every splatting method; that pattern usually means they were not tuned for real data rather than that they are 30 dB worse. And the reference volumes are themselves reconstructions, as the authors acknowledge, so differences of a fraction of a dB may fall inside the reference's own error. Neither point is fatal, but both are cheap for the authors to clarify in a rebuttal.
Questions for authors
see above
3 comments
Response to Reviewer mhZL (2/3)
Q3. The ablation does not isolate the proposed primitive. In the controlled comparison of Table 2, KB kernels improve on a matched Gaussian by 0.04–0.12 dB and run 8% faster; the headline numbers in Table 1 are 0.93 dB and about over R$^2$-Gaussian. The gap between those two settings is the issue: most of the improvement would then have to come from population control, initialisation or implementation detail rather than from the basis itself — which is the paper's central claim.
We agree that the matched primitive comparison and the comparison against R$^2$-Gaussian measure different effects. The Gaussian control in Table 2 tests a change of primitive within a common reconstruction framework, whereas R$^2$-Gaussian is a complete method with its own rendering, optimization, and population-control implementation. The larger improvement over R$^2$-Gaussian therefore cannot be attributed entirely to replacing the Gaussian primitive.
Following your suggestion, we expanded the ablation to 12 Loop-X scans at 50% and 25% views and three random seeds. The matched study compares Gaussian, fixed- and learned-concentration truncated Gaussian, and fixed- and learned- KB primitives. For the primitive-only comparisons, we hold projection data, losses, population budgets, and training schedules fixed. We also retain an ordinary learned- KB control alongside the joint density–scale–concentration update to measure the optimizer's contribution separately.
To test reconstruction guidance, we compare selected-view FDK initialization with guided allocation, the same initializer with unguided allocation, and random initialization with unguided allocation. The last condition uses no reconstructed volume for initialization or placement. We further compare physical per-ray integration along each detector pixel's source-to-detector ray with the baseline center-ray approximation, keeping the remaining settings fixed within each primitive family. These controls separate the effects of the primitive, concentration learning, initialization, continued guidance, and rendering approximation.
Tables 4–5 report the paired attenuation-PSNR difference between learned- KB and the matched Gaussian control as dB, together with their training times and variability across seeds. The expanded ablation table is reproduced above for your convenience.
Response to Reviewer mhZL (3/3)
Q4. Two things around the baselines and the reference volumes need a direct answer. The neural baselines land near 15 dB, some 30 dB below every splatting method; that pattern usually means they were not tuned for real data rather than that they are 30 dB worse. And the reference volumes are themselves reconstructions, as the authors acknowledge, so differences of a fraction of a dB may fall inside the reference's own error. Neither point is fatal, but both are cheap for the authors to clarify in a rebuttal.
We thank you for identifying this discrepancy. After an extensive audit of all neural methods, we identified inconsistent PSNR peak conventions: the neural baseline evaluator uses a reference-percentile intensity range, whereas the splatting evaluator uses a fixed attenuation peak. We corrected this mismatch by recomputing neural PSNR from the saved attenuation RMSE under the same fixed-peak convention. The updated LoopX neural averages are approximately 41–43 dB, eliminating the apparent 30 dB gap. We updated all quantitative and qualitative results accordingly.
Regarding the CT references, the reported differences measure agreement with reconstructed reference volumes. Although the reference volumes are reconstructions rather than independent attenuation ground truth, the accompanying acquisition metadata, measured scan geometry, and noise profile make them well-characterized estimates of the underlying attenuation structure. They therefore provide a strong practical basis for evaluating reconstruction fidelity, while retaining some uncertainty from acquisition noise and reconstruction artifacts.
Response to Reviewer mhZL (1/3)
Thank you for acknowledging our argument for a more expressive primitive in volumetric CT reconstruction. We also appreciate your thoughtful recognition of the value of our dataset. Our goal is to provide a rendering pipeline and a dataset that will progress the field.
We agree that aggregate scores alone do not show how reconstruction quality varies across scans and scanners. Following your suggestion, Tables 6–11 now report results for each anatomy and inanimate object, grouped by dataset and acquisition system, alongside the corresponding baseline results. This makes case-specific outcomes explicit, including the original Neck result in which R$^2$-Gaussian achieved higher PSNR. For our expanded ablation in Table 2, we report means and sample standard deviations over three random seeds, showing both the average differences between configurations and their variability across repeated runs. The table is reproduced above for your convenience.
We agree that the original 50% and 25% settings do not fully test reconstruction in the few-dozen-views regime. We have therefore extended training and evaluation to 10% (27–80 projections) and 5% (14–40 projections) of the available views. Tables 6–11 now give the exact projection count for each scan, since the number of acquired views differs across datasets. All methods use the same selected projections for each comparison. These additional settings test clinically sparser acquisitions and show how reconstruction quality changes as fewer views are available. We report per-case results and provide corresponding reconstructions and error maps in Figures 7–22.