- Rating
- 1
- Confidence
- 4
- Informativeness
- 1
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
The paper targets electron density prediction. They use the GTO auxiliary basis formulation of SCDP (Fu et al., 2024), which regressed the GTO coefficients with an eSCN architecture, by an EquiformerV3 (Liao et al., 2026) trained with flow matching. They use two flow steps during generation.
Critical strengths
- Slight improvement (~10% lower NMAE) on QM9 over SCDP + VO, L = 6 (Fu et al., 2024). But it is unclear if that is because of the different architecture or because of using two flow steps instead of direct prediction, especially since the proposed method is 1.6x slower.
Critical weaknesses
- No innovation. The paper swaps out the backbone for a newer architecture, and uses two flow steps instead of directly regressing
- The writing is verbose and claims known tricks it's innovations. E.g.
- the "Two-Phase Trajectory Curriculum Learning" is half a page in methods, when they are really just training on the same flow times that they use during inference (Euler integration).
- using equivariant networks ("Equivariant Flow and Isotropic Irrep Priors" in methods) is hardly their invention, but doesn't even cite any prior work.
- verbose AI language throughout the paper
Questions for authors
- Does table 4 use a different validation set then table 1? If yes, can you add SCDP + VO, L = 6 (Fu et al., 2024) to table 4, to compare it to the direct regression (deterministic, single-step loss)?
- I don't understand the ablation of flow steps (Euler integration). It seems to sweep over training integration steps (phase-2) and inference steps separately. Why? Wouldn't it make more sense to keep them tied, and test more flow steps together? I don't see why more flow steps could reduce the accuracy
4 comments
Continued Response to Reviewer ae4a
the "Two-Phase Trajectory Curriculum Learning" is half a page in methods, when they are really just training on the same flow times that they use during inference (Euler integration).
We agree with this description. Phase 2 trains the model on the same Euler steps it uses at inference, and the revised method section describes it more briefly.
We see this simplicity as a practical advantage rather than a weakness. Phase 2 keeps the same network and the same parameters, and adds no teacher, no extra conditioning input and no inference cost. The model is run with the same two steps before and after it. This change alone lowers the error on the 10% subset from 0.295% (Phase 1 only) to 0.240%, and from 0.280% for direct regression with the same backbone. The two phases also matter in practice, since starting Phase 2 from Phase 1 reaches the accuracy of the alternatives in Table 5 with less compute (74 GPU-h against 81 to 182).
using equivariant networks ("Equivariant Flow and Isotropic Irrep Priors" in methods) is hardly their invention, but doesn't even cite any prior work.
We agree and now cite this work (Köhler et al. 2020, Xu et al. 2022, Hoogeboom et al. 2022, Klein et al. 2023, Song et al. 2023). The revision presents the isotropic prior over the irreps of the GTO coefficients as a design choice rather than a contribution, and Proposition 1 is now a short remark.
verbose AI language throughout the paper
As stated in our LLM usage disclosure, language models were used to organize and polish the text, and all content and results were checked by the authors. In the revision we removed claims the experiments do not test, such as "eliminate discretization drift" and "straightens the flow field", replaced general statements with numbers, and shortened the method section and the introduction. We would welcome pointers to passages that still read as verbose.
Does table 4 use a different validation set then table 1? If yes, can you add SCDP + VO, L = 6 to table 4, to compare it to the direct regression (deterministic, single-step loss)?
No, both tables use the same 50 validation molecules. Table 4 trains and tests on the fixed 10% subset of the standard training and test sets, which is why its errors are higher. As requested, SCDP+VO (L=6) trained on the same subset with the same budget is in the second table of our first answer.
It seems to sweep over training integration steps (phase-2) and inference steps separately. Why? Wouldn't it make more sense to keep them tied, and test more flow steps together? I don't see why more flow steps could reduce the accuracy.
The sweep over training integration steps is already tied, since a model trained with K steps is also tested with K steps. On the 10% subset it gives 0.296%, 0.240% and 0.240% for K = 1, 2 and 3 (K=2 is OrbFlow, K=1 and K=3 are the last two rows of Table 14 in the revision), so accuracy saturates at K=2. We will add K=4 to the final version as suggested, and the caption now says that the steps are tied.
More steps hurt only in the separate inference sweep (Appendix E.4), which runs the K=2 model with more steps than it was trained with. The network predicts the endpoint, so the last Euler step returns its prediction at t = 1 − 1/K. Phase 2 trains t = 0.5 but no later time, so the error rises with more steps (0.539% at K=4). A model trained only with the single-step loss does not degrade with more steps (0.290% at K=2, 0.284% at K=16), but it never beats regression (0.280%). OrbFlow should therefore be run with the number of steps it was trained with.
We hope these controlled experiments address the reviewer's main concern, and we would be grateful if the reviewer would reconsider the score in light of them.
# Follow-up to Reviewer ae4a
We thank the reviewer again for the helpful review. As the discussion period ends in two days, we briefly recall our main answers.
- Architecture or training. With EquiformerV3 fixed, direct regression reaches 0.174% on full QM9 and OrbFlow 0.152%, against 0.178% for SCDP+VO, so about 85% of the improvement comes from the training. Two flow steps alone do not explain it, since a deterministic two-step model reaches 0.268% against 0.240% for OrbFlow (Table 4).
- Novelty. The contribution is a training method that trains the model on its own few-step rollout from noise. It keeps the network unchanged and lowers the error at a fixed backbone by 13% on full QM9.
- Speed. The 1.6× latency comes from the two Euler steps, the smallest number at which accuracy saturates.
- Citations and writing. The revision cites prior equivariant flow models and removes claims the experiments do not test.
We would be very grateful to know whether these answers address the reviewer's concerns, and we are happy to clarify anything further.
Dear Reviewer ae4a,
We understand this is a busy time and thank you again for your review. As the discussion period ends tomorrow, we would be very grateful to hear your thoughts on our responses, in particular whether the evidence that most of the improvement comes from the training, at a fixed backbone, addresses your concerns about novelty and contribution. If any questions remain, we would be glad to clarify them before the deadline.
Thank you very much for your time.
Response to Reviewer ae4a
We thank the reviewer for the clear questions. The new experiments show that OrbFlow's gain over SCDP+VO comes from how it is trained, not from the newer backbone, and that on QHFlow2's network the same training beats QHFlow2's own recipe.
Regarding the size of the improvement, OrbFlow lowers the error of SCDP+VO by 14.6% on QM9 (0.178% to 0.152%) and by 51% to 63% on each of the six MD molecules (Table 2). The gain is largest on MD and its size depends on the dataset, but it is consistent, since OrbFlow improves on SCDP+VO on QM9 and on every MD molecule.
Regarding the 1.6× slowdown, this is the MD latency (0.066 s against 0.041 s per molecule, Table 12), and on QM9 the ratio is 1.4× (0.33 s against 0.23 s, now in Section 4.5). The overhead comes from the Euler integration of the flow. OrbFlow evaluates the network once per Euler step, so its two-step rollout needs two forward passes where direct regression needs one. This adds 0.025 s per molecule on MD and 0.10 s on QM9, while building the density on the grid costs the same for both models.
The gain comes from the training, not from the architecture, and two flow steps alone do not explain it. We show this in two ways.
First, Table 4 fixes the backbone, basis, loss and training budget and changes only the starting point and the training loss. Like our other ablations, it uses a fixed 10% subset of QM9 (12,384 training and 1,000 test molecules), because a full QM9 run costs about 1,600 GPU-h and each ablation needs three seeds. All values are NMAE in %.
A deterministic second pass helps little (0.268%), and starting from noise alone does not help (0.295%). Only both together, a noise start and training on the model's own two-step rollout, lower the error by 14% (0.280% to 0.240%).
Second, we separated the backbone from the training on full QM9 by training EquiformerV3, OrbFlow's backbone, by direct regression (500k steps, against 450k for OrbFlow). We also trained SCDP+VO on the 10% subset, as the reviewer asks below. All values are NMAE in %.
On full QM9, changing only the backbone lowers the error from 0.178% to 0.174%, while changing only the training lowers it from 0.174% to 0.152%. About 85% of the improvement therefore comes from the training. On the 10% subset, at the same 90k-step budget as all other ablations, eSCN is further behind (0.327% against 0.280%). Its validation error was still falling at the end of training, so part of this gap is slower convergence. The training gives a similar reduction on top (0.280% to 0.240%). With the full training set, both backbones converge, the backbone difference almost vanishes, and the gain comes from the training.
As shown above, neither the backbone nor the extra step explains the gain. The contribution is the training. The model starts from noise and is trained on the same few-step rollout it runs at inference. The change is simple, as are consistency models (Song, Dhariwal, Chen and Sutskever, 2023) and shortcut models (Frans et al., 2025), which also change only how a flow model is trained and keep the network. Like them, it matters because of what it gains, namely 14% at a fixed backbone and 85% of OrbFlow's improvement over SCDP+VO on full QM9.
The training also works on other networks. On QHFlow2's network (details in our reply to Reviewer cVZC), it reaches 0.240%, against 0.255% for QHFlow2's own flow-matching recipe. To our knowledge, training the few-step rollout of a flow model on the density loss is new for density and Hamiltonian prediction. QHFlow and QHFlow2 train only at single interpolated times.