- Rating
- 4(+1)
- Confidence
- 4
- Informativeness
- 3
- Presentation
- 3
- Soundness
- 3
Read review
Paper summary
The paper presents RIFT, a framework for radar novel-view synthesis and 3D reconstruction using only radar measurements and calibrated sensor poses. It represents a scene as learnable scattering points with direction-dependent complex responses. A physics-based radar model predicts measurements, and the scene representation is optimized by matching these predictions to the observed signals. The method gradually increases spatial and directional detail during training. The same learned representation supports both signal prediction at new viewpoints and geometry reconstruction. Experiments use simulated data and real measurements from the GOTCHA dataset.
Critical strengths
- The adaptive representation is a useful design. The method uses training gradients to decide where to add spatial detail and more complex directional responses. This provides a concrete way to adjust the representation to the observed measurements.
- The experimental evaluation is extensive. The paper includes experiments on both simulated and real radar data, comparisons with multiple baselines, and a broad set of metrics covering signal prediction and 3D reconstruction. The detailed results and additional visualizations in the appendix provide a thorough assessment of the method.
Critical weaknesses
- The novelty needs clearer positioning against related work. The paper should cite and discuss RFDT [1], mmIR [2], which address closely related problems involving differentiable RF rendering, complex radar synthesis, and scene recovery. The general idea of recovering scene parameters by matching simulated and measured RF signals is already established. RIFT’s contribution therefore appears to lie primarily in its adaptive spatial and angular representation and its specific optimization strategy. However, the individual benefits of these designs are not sufficiently demonstrated through controlled ablations.
- The main paper contains too few visual results. Many useful visualizations are placed in the appendix, making it difficult to understand the method’s benefits and assess the results from the main text alone. The authors should move more representative reconstruction and novel-view synthesis comparisons into the main paper, including comparisons with existing methods. This would make the paper easier to follow and its improvements more convincing.
- The fairness of the qualitative comparisons needs clarification. Several baselines produce very poor visual results, raising concerns about whether they were reproduced correctly. Radar methods can be sensitive to implementation details and data processing, so these results may reflect reproduction issues rather than limitations of the original methods. I recommend restricting the main comparison to methods with official implementations that support the same dataset, using a consistent evaluation protocol. Any adapted or reimplemented baselines should be clearly identified and validated before their visual results are used to support claims of superiority.
[1] Xingyu Chen, Xinyu Zhang, Kai Zheng, Xinmin Fang, Tzu-Mao Li, Chris Xiaoxuan Lu, and Zhengxiong Li. “Physically Accurate Differentiable Inverse Rendering for Radio Frequency Digital Twin.” In MobiCom 2026. [2] Adnan Armouti, Yixuan Gao, and Rajalakshmi Nandakumar. “mmIR: Frequency-Space Inverse Rendering for 3D Millimeter-Wave Radar ADC Synthesis.” In ECCV 2026
Questions for authors
What checks were performed to validate the adapted baseline implementations? In particular, please clarify the validation of the PyTorch ports of Radar Fields and RadarSplat, and the decision to keep GeRaF’s model step at zero, which prevents its scheduled updates from progressing.
4 comments
Official Comments to Reviewer XE1v (Part 2 of 2, Round 1)
Question (validation of the adapted baselines). Radar Fields: tiny-cuda-nn is CUDA-only, so we run an fp32 PyTorch re-implementation of its encodings and networks, with the same layout and parameter counts as the original. Checked against the real tiny-cuda-nn on an H100, its encodings agree with the fp32 encodings to within 3.0e-5 and the outputs of the full model to within 5.1e-4 (relative); its initialization and gradient reduction still differ from the original backend. RadarSplat: its rasterizer and fused-SSIM operations are CUDA-only, so we ported them to PyTorch with their backward passes. On saved inputs of a real B787 target, against the fp32 CUDA reference, every operation is identical or within 1.5e-7, the rasterized products are within 2.9e-5, the loss within 3.4e-7 (relative) and the parameter gradients within 7e-4 (relative L2). We did not compare training trajectories with the original CUDA implementations or reproduce the original papers' results on their own datasets.
GeRaF's model step. In the submission we kept the model step at zero, as the released runner does, so its annealing and sharpness schedules stayed at their initial values. In the updated experiments the step advances: GeRaF is trained with the schedules stretched to our 360,000 updates (annealing ends at 360,000, sharpness unfreezes at 72,000; the release uses 50,000 and 10,000) on all six objects and three training seeds, 18 runs, under one declared variant (gradient clip 3, a zero gradient for the matched-filter magnitude where the prediction is exactly zero, and a non-finite guard):
| GeRaF, mean over the six objects | Complex RelMSE (%) | Range-power RelMSE (%) |
|---|---|---|
| Step held at zero (released runner), seed 42 | 148.0 | 18.91 |
| Step advancing, seed 42 | 152.9 | 23.34 |
| Step advancing, mean of three seeds (GeRaF row of Table 1) | 167.4 | 18.24 |
Advancing the step does not change the picture: the complex RelMSE is above 100% in all 18 runs (123.9% to 215.6%), and these runs replace the earlier GeRaF row of Table 1.
What these checks mean. They validate the operations and losses of the ports, not the end-to-end behavior of the adapted methods, and none of this diminishes the contribution of the works we compare to. GeRaF, Radar Fields and RadarSplat were designed mainly for azimuthal views, with native observables organized in range and azimuth, and are trained on matched-filtered power or amplitude; our comparison evaluates them as adapted to our setting (Section 5), and their entries characterize our adaptation under this paper's budget and radar presentation, not the methods in their own settings (Appendix F). Our claim is limited to one problem: solving 3D reconstruction and radar novel-view synthesis together, from the same radar responses and within one representation. On that problem RIFT scores best in every column of Table 1 on the RIFT dataset and in every column but IoU of Table 2 on GOTCHA, against the baselines as adapted here.
We are grateful for your thoughtful suggestions, which helped us strengthen the manuscript during revision.
Best, Authors
The authors have addressed the main concerns about the method, baseline comparisons, and evaluation. I recommend accepting the paper.
Response to Reviewer XE1v
Dear Reviewer XE1v,
Thank you for taking the time to read our response. We’re glad we addressed your main concerns, and we appreciate your recommendation. Thanks to your review, we were able to explain the method more clearly and give a fuller account of the baseline comparisons and evaluation. We believe these revisions strengthened the paper.
Best, Authors
Official Comments to Reviewer XE1v (Part 1 of 2, Round 1)
Dear Reviewer XE1v,
We appreciate your constructive feedback on our work. Here is a point-by-point response to the weaknesses and the question you brought up, posted in parts.
Weakness 1: We thank the reviewer for the two references. We will cite and discuss RFDT (Chen et al., MobiCom 2026) and mmIR (Armouti et al., ECCV 2026) in the related work of the revised paper, and position RIFT relative to them. For the individual benefits of the adaptive spatial and angular representation and of the optimization, please see the ablation study in the new Appendix H (Tables 10-15, summarized in Section 5.2), which changes one choice of the main recipe at a time on A320, B787 and the race car. In short, the signal depends mainly on the angular unlocks (3.3-3.9 times worse without them), the group-sparse prior (38-47 times) and the backprojection start (6-9 times on A320 and the race car).
Weakness 2: We agree that the visual comparison should be visible in the main text. The main text is at its page limit, so the 3D reconstruction and view comparisons with the baselines are in the appendix (Figs. 8-10 for the RIFT dataset, Figs. 12a-14c for GOTCHA). In the revised paper we will add a compact reconstruction comparison with the baselines to the main text within the page limit.
Weakness 3: We agree that adapted or re-implemented baselines must be identified, and that their visual results can reflect the adaptation and not the original method. Backprojection is standard; Radar Fields and RadarSplat use their released code with PyTorch ports of their CUDA-only operations (validation details below); for SpINRv1, GeRaF 1.0 and Sugavanam-Ertin we did not locate official implementations, and we implemented SpINR-style from the paper, GeRaF 1.0 from the released stage-1 components with the settings of the v1 paper, and Sugavanam-Ertin from the equations. Section 4 and Appendix F list what we retain and change for each method, and Section 5 states that the comparison evaluates the methods as adapted to our setting. No baseline has an official implementation that supports our data, the full-sphere multi-frequency responses of an isolated object, so none runs unchanged and a restriction to such methods would leave only backprojection. RIFT and the four learned baselines follow one protocol (the same 2,400 training views, 360,000 updates, the minimum-validation checkpoint and three training seeds) and are scored on the same reserved-test views with the same metrics.
Our response continues in Part 2 of 2.