- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
This paper addresses 3D smoke reconstruction from a video taken with one fixed, calibrated camera. Instead of synthesizing missing camera views, it learns a prior over 3D density. An autoencoder represents the density in a monoplanar latent space, and an image-conditioned diffusion model learns to generate plausible latents. At test time, the frozen model is sampled with rendering feedback from the input view and constraints between nearby frames. A final, sequence-specific optimization fits density corrections, smoke inflow, and a divergence-free DFK velocity field using image and transport losses. The experiments examine novel-view rendering, velocity estimation, and re-simulation on Plume and ScalarFlow.
Critical strengths
-
The Plume reconstruction is convincing in the shown sequence. The supplementary Plume15 clips show frames near 55, 74, and 93. The predicted plume keeps its overall head and stem in both the input and held-out views, including during cumulative replay. Several baselines shown in the same clips become much blurrier or lose the plume shape. This agrees with the reported Plume held-out PSNR: 34.10 dB for reconstruction and 34.92 dB for re-simulation, versus 30.04 and 28.73 dB for the strongest listed alternatives in Table 2. These videos are selected examples, and I have not independently reproduced the numbers.
-
The paper makes a useful attempt to separate density quality from the physical refiner. The shared Stage-3 comparison reports a Plume velocity cosine of 0.496 for this method versus 0.188 for the best listed shared-refiner alternative. The ablations are informative: removing diffusion lowers held-out reconstruction PSNR from 34.10 to 25.00 dB, while removing temporal-window synchronization lowers it to 32.49 dB. These results support the role of the learned density prior and temporal coordination.
Critical weaknesses
-
I cannot reconcile the ScalarFlow evaluation numbers. Tables 2 and 4 say they evaluate the recorded held-out cameras and report 32.99 PSNR / 0.956 SSIM / 0.081 LPIPS for Ours. Table 6 assigns exactly those values to 360-degree views rendered from reference volumes, but reports 33.80 / 0.9724 / 0.0789 for Ours in its recorded-camera row. The text in Appendix B.4 again says Tables 2 and 4 use recordings. Perhaps one table is mislabeled or contains values from a different run. As written, I cannot tell which evidence supports the main ScalarFlow comparison.
-
The supplementary videos do not settle the broader physical claims. The ScalarFlow velocity and cumulative replay examples are labeled sim094, within the paper's sim010–103 training split. In the replay video, Ours is labeled 'Post-processed preview' and has no displayed PSNR, unlike the baselines. The crosswind example applies the same spatial warp to the rolled-out densities and the reference; it does not test a rollout under a new wind force. These demonstrations are useful, but they provide narrower evidence than a held-out ScalarFlow replay or a genuine force-change experiment would.
Questions for authors
-
Which ScalarFlow results in Tables 2, 4, and 6 are measured against recorded camera images, and which are measured against rendered reference volumes? Why do 32.99 / 0.956 / 0.081 appear under both descriptions, while Table 6 gives another recorded-camera result of 33.80 / 0.9724 / 0.0789? Please provide the corrected mapping of numbers, scenes, cameras, frames, and reference images.
-
Could the authors show an unprocessed reconstruction and cumulative replay from a held-out ScalarFlow scene (sim005–009) in the camera setting used for the main table? Please also explain the choice of sim094 for the current clips and what 'Post-processed preview' means for Ours.
-
In the crosswind experiment, is wind introduced into the velocity/transport calculation, or is the stated warp applied after rollout? If it is the latter, the result would be better described as a warped replay than as evidence of response to an unseen force.
3 comments
Thank you for the detailed response and the substantial revisions. The authors have corrected the original ScalarFlow protocol description, rerun the FluidNexus baseline with the official ScalarFlow checkpoint and recorded input videos, replaced the training-scene supplementary example with a held-out scene, and clarified the stepwise crosswind re-simulation procedure.
These changes substantially improve the submission. The Plume results, ground-truth velocity evaluation, shared Stage-3 comparison, and ablations continue to support the value of density-space completion for monocular smoke reconstruction. The new ScalarFlow loss ablations also provide useful evidence that transport, mass, and vorticity terms contribute on real captured smoke. The crosswind experiment is now clearer: the density perturbation is applied after each advection step and is propagated into the next step, rather than being applied only to already completed frames.
However, I still have a concern about the final consistency of the central ScalarFlow results. Tables 2, 4, and 6 report the Ours test-view reconstruction metrics as 32.99 dB / 0.956 SSIM / 0.081 LPIPS, whereas the corrected ScalarFlow full-pipeline row in Table 7 reports 32.99 dB / 0.948 SSIM / 0.087 LPIPS. If the Table 7 values are the corrected final evaluation, the method does not outperform FluidNexus on SSIM (0.948 versus 0.9559), despite the broader claim of leading on all metrics. The PSNR and LPIPS results remain strong, but the manuscript should not leave these two final metric sets inconsistent.
The revised crosswind experiment strengthens the evidence for transporting a prescribed density edit through the recovered field, but it is not a test of a newly inferred velocity response to an unseen external wind force. The velocity field is still fitted within the observed interval, and the perturbation is a prescribed density displacement applied during rollout. This result should therefore be interpreted as evidence of robustness under a controlled downstream density edit, not as validation of unknown-force dynamics.
Overall, the authors have made meaningful progress and the method has clear technical value. Nevertheless, the unresolved inconsistency in the central ScalarFlow evaluation affects the interpretation of the main real-data comparison. I therefore maintain my recommendation of weak rejection (2), with confidence 3. This is a borderline recommendation rather than a clear rejection: the Plume evidence and the corrected parts of the ScalarFlow evaluation are promising, but the final quantitative claims should be internally consistent before acceptance.
We sincerely thank the reviewer for their exceptionally careful and patient assessment throughout the rebuttal process, and we apologize for this inconsistency and the oversight in our revisions.
During the rebuttal period, we reran the full set of ablation experiments on a different machine with the same hardware configuration, with the results given in Table 7. To ensure consistency, we also reran our complete pipeline, which produced slightly different numerical results from those in our original submission. Unfortunately, we acknowledge that we were not sufficiently careful in preparing our rebuttal revisions and failed to synchronize these updates across all tables. We apologize for this oversight and sincerely appreciate the reviewer's careful attention in identifying it.
We have chosen to retain the latest results, despite their slightly lower scores, and have updated Tables 2, 4, and 6 to be consistent with Table 7. The corrected ScalarFlow results are:
| Method / version | PSNR ↑ | SSIM ↑ | LPIPS ↓ |
|---|---|---|---|
| Ours — updated | 32.99 | .948 | .087 |
| FluidNexus — reproduced | 31.36 | .956 | .140 |
| Ours — originally reported | 32.99 | .956 | .081 |
We fully acknowledge that our updated SSIM is lower than FluidNexus, while our PSNR and LPIPS remain better. We have made an initial round of revisions throughout the manuscript to reflect these corrected results and clarify our claims. However, we recognize that this revision during the rebuttal may not have been sufficiently thorough yet. In the next revision, we will carefully review the entire manuscript word by word, verify the consistency of all reported results, and further narrow our claims to ensure they are fully supported by the evidence.
We also appreciate the reviewer's clarification regarding the crosswind experiment. We agree and apologize for the imprecise wording. The test scene is unseen during training, whereas the external crosswind force is known and prescribed, with its effect represented by a density-displacement correction during rollout. The recovered velocity remains fitted to the observed interval; we do not infer an unknown force or a new velocity response. The results support transporting this prescribed perturbation through the recovered field on the held-out test scene, without establishing unknown-force dynamics. We have made an initial clarification and will further refine the description to avoid overstating the implications of this experiment.
We are genuinely grateful for the reviewer's patience, thoroughness, and constructive criticism. Their careful feedback has helped us identify important shortcomings in our revisions and improve the accuracy and clarity of our submission.
Response to Reviewer 1fAL
We thank the reviewer for the careful and constructive evaluation. We sincerely apologize for the inconsistencies in our original presentation. We have corrected the tables, rerun the relevant evaluations, and updated the supplementary material.
ScalarFlow evaluation and Tables 2, 4, and 6.
We acknowledge errors in Table 6 and the FluidNexus entries in Tables 2 and 4. Our earlier FluidNexus evaluation used images rendered from multiview-reconstructed ScalarFlow volumes, which were mistakenly included in the recorded-camera comparison.
We have rerun FluidNexus using its official ScalarFlow checkpoint, original recorded videos, and matched input/test cameras. The evaluation uses held-out scenes sim005--009, frames 50--149, with calib3 as input and calib1/2/4/5 as test views. FluidNexus achieves 31.36 dB PSNR / 0.9559 SSIM / 0.1402 LPIPS, compared with 32.99 / 0.956 / 0.081 for VolSmoke. These FluidNexus scores are our reproduced results, not values quoted from the original paper.
We also corrected Table 6, where our recorded-camera and full-orbit reference-render results were inadvertently placed in the wrong rows. The corrected recorded-camera result (32.99 / 0.956 / 0.081) now agrees with Tables 2 and 4. The full-orbit reference-render setting is reported separately (32.87 / 0.950 / 0.088), with both protocols clarified in Appendix B.4. They remain substantially better than FluidNexus's 29.63 / .882 / .151, including a 3.24 dB PSNR advantage. We have corrected the reference-render entries and clarified both protocols in the manuscript.
We sincerely apologize for the earlier evaluation inconsistencies and appreciate the reviewer for identifying them. After correcting the protocols and rerunning FluidNexus, the revised results continue to support the effectiveness of VolSmoke on held-out real-world ScalarFlow data.
ScalarFlow supplementary videos and "Post-processed preview."
We inadvertently included the training scene sim094 in our earlier supplementary examples. Both the cumulative re-simulation video and velocity-field visualization have now been replaced with results from the held-out test scene sim006. Our quantitative tables use the official ScalarFlow test-scene split.
The label "Post-processed preview" referred to the final output after Stage 3 physical refinement, which is an integral part of our standard reconstruction pipeline, rather than an additional post-processing procedure. We have removed this ambiguous label and updated the PSNR annotations in the re-simulation video.
These revised videos provide direct visual evidence of velocity recovery and cumulative transport on a genuinely held-out ScalarFlow scene.
Crosswind re-simulation.
The crosswind perturbation is implemented as a lateral density displacement applied after every advection step. Each sequence is rolled out from its initial density, and the perturbed density becomes the input to the next advection step. The GT density is independently rolled out using its reference transport under the same perturbation schedule.
Thus, each perturbation influences subsequent transport, rather than being applied independently to frames of an already completed rollout. The low error relative to the correspondingly perturbed GT rollout demonstrates that our reconstructed fields can sustain accurate re-simulation under additional perturbations. We have clarified this procedure in the manuscript and supplementary material.
We sincerely appreciate the reviewer's detailed examination, which helped us identify and correct these issues. The corrected evaluations and new held-out supplementary results strengthen the experimental evidence while preserving our main conclusions regarding density reconstruction, velocity recovery, and transport consistency.
We hope these revisions address the reviewer's concerns about the reliability of our evaluation and would welcome any further questions.