- Rating
- 3(+1)
- Confidence
- 3
- Informativeness
- 3
- Presentation
- 3
- Soundness
- 2(+1)
Read review
Paper summary
This paper proposes ReacFlow, a two-stage framework that generates complete reaction pathways from reactant and product structures. Its main idea is that accurate reconstruction alone does not mean that latent representations are easy to predict from endpoint conditions. To address this, the tokenizer uses reconstruction together with CI-NEB-inspired search-response supervision and endpoint-anchored interval completion. After the tokenizer is frozen, a latent flow model learns to turn the endpoint-linear pathway representation into the reference pathway representation. It uses flow-matching and decoded-geometry losses for training. Inference needs four velocity-network evaluations and no force calculations. Tests on Transition1x and Halo8 include geometry and energy metrics, controlled pretraining ablations, latent-error diagnostics, and a comparison with direct completion. Conditional error bounds provide theoretical support for the design.
Critical strengths
- A key strength is that the paper recognizes that accurate autoencoder reconstruction alone does not mean that latent representations are easy to predict from endpoint conditions. The paper builds its pretraining strategy around this problem. It combines CI-NEB-inspired search-response supervision with interval completion that includes the endpoint-linear input used during generation. Together, these objectives are designed to help the tokenizer keep physically relevant information and support downstream conditional prediction. I find the clear link between the problem and the proposed training objectives especially convincing. The framework also offers efficient inference, generating complete pathways with four velocity-network evaluations and no force calculations.
Critical weaknesses
- The Drift-React results in Table 1 do not match those in the cited paper, while the other baseline results are exactly the same. The paper states that the baseline results were taken directly from that work, but does not clearly explain this difference. This unexplained difference greatly reduces my confidence in the reported comparison. In its current form, I cannot rely on Table 1 as evidence that ReacFlow performs better than existing methods.
Questions for authors
I see value in the proposed approach, but the unclear baseline comparison raised in the first question strongly affects my current assessment. A clear explanation supported by evidence could change my recommendation. Answering the endpoint-alignment question would further increase my confidence that the method can be used in practice and strengthen the case for acceptance.
- Please explain why the Drift-React results in Table 1 differ from those in the cited paper, while the other baseline values remain unchanged. This seems to conflict with the statement that all baseline results were taken directly from that work. Where exactly did the reported Drift-React values come from, and were any changes made to them? Please provide supporting calculations or evaluation code to show that these values are correct. Also, please clarify whether the claimed improvements still hold when the same evaluation rules are applied.
- Please clarify the endpoint alignment assumptions. Does the method require a specific relative alignment between the reactant and product structures? Is any rigid alignment performed before building the endpoint-linear path? If the method is meant to work with independently prepared endpoint structures, could you provide a small sensitivity test that rotates or translates only the product structure? The evaluation should account for the changed endpoint coordinates. Otherwise, please state the required alignment and explain how the benchmark inputs meet this requirement.
8 comments
Shared evaluation protocol. Generated-geometry results follow the benchmark conventions in manuscript Appendix C.1, including Tables R1–R6, the common evaluation of reruns in Table R10, the input-placement experiment in Table R14, and the additional diagnostics in Tables R16–R18. Each metric uses the same scoring rule across compared methods and tables, with metric-specific alignment as specified below.
| Item | Rule |
|---|---|
| Evaluation inputs | The same benchmark reaction IDs, reference paths, and ten-frame grids within each dataset comparison; padding is excluded using valid-atom masks. Any restricted subset is identified explicitly. |
| Atom correspondence | Fixed according to the benchmark atom mapping; no atom rematching. |
| Alignment | TS-RMSD takes the smaller aligned RMSD obtained with and without mirror reflection. IRC-RMSD and Fréchet use centered, proper-rotation Kabsch alignment (determinant +1), without reflections. |
| Normalization | Per atom: the squared coordinate residuals are summed over the three coordinates and valid atoms, divided by the number of valid atoms N, then square-rooted. |
| TS-RMSD / reference-peak RMSD | For a full path, compare generated and reference structures at the first maximum of the reference energies over all ten frames. Predicted energies are not used to select this frame. A TS-only method's predicted structure is compared with this same reference structure. |
| IRC-RMSD | Average the aligned corresponding-frame RMSDs over all ten frames, including both endpoints. |
| Fréchet | Discrete Fréchet distance over complete paths, using proper-rotation, per-atom RMSD as the point distance. |
| Aggregation | Reactions are equally weighted, with no error-based trimming of geometry scores. Measured SDs describe variation across reactions. |
“TS-RMSD” and “reference-peak RMSD” refer to the same scoring rule above. The released evaluator specifies TS mirror handling and proper-rotation path alignment separately. Clean reconstruction remains raw, per-atom RMSD over all ten frames in the common coordinate frame, before endpoint restoration and without independent alignment. Training losses retain their per-coordinate convention; the SO(3), eight-internal-frame Path diagnostic in Appendix C.2 is separate from benchmark IRC-RMSD.
Evaluation provenance. Table R10 evaluates predictions from our reruns of both models under the shared protocol; its ReacFlow scores agree with the manuscript values at the reported precision. Table R9 documents the historical normalization correction to source-reported statistics. MolGEN's single-sample, all-candidate mean, and reference-selected best-of-30 results are distinguished explicitly; its published energy-selected result is a separate literature value.
Reruns and common evaluation. We independently retrained DriftReact using its released implementation, retaining the original training data, configuration, and checkpoint-selection procedure, with training seed 42. We reran ReacFlow and evaluated both methods with a shared evaluator using the same reaction IDs, reference paths, ten-frame grids, and valid-atom masks. Metric-specific alignment and per-atom normalization follow manuscript Appendix C.1 and the shared protocol above. DriftReact's reproduced mean geometry errors are close to the corrected source values in Table R9, with relative deviations of approximately 0.8–1.9% across the six dataset–metric pairs, computed from the displayed rounded means. ReacFlow's scores agree with the manuscript values at the reported precision.
Table R10. Rerun results for both models under the shared evaluation protocol. Mean ± reaction-level SD.
| Dataset | Method | Reference-peak RMSD ↓ | IRC-RMSD ↓ | Fréchet ↓ |
|---|---|---|---|---|
| Transition1x | DriftReact | 0.264 ± 0.163 | 0.225 ± 0.125 | 0.464 ± 0.262 |
| Transition1x | ReacFlow | 0.215 ± 0.143 | 0.155 ± 0.118 | 0.260 ± 0.215 |
| Halo8 | DriftReact | 0.188 ± 0.152 | 0.125 ± 0.111 | 0.216 ± 0.193 |
| Halo8 | ReacFlow | 0.175 ± 0.128 | 0.165 ± 0.126 | 0.280 ± 0.231 |
Under these shared rules, ReacFlow has lower means for all three metrics on Transition1x. On Halo8, ReacFlow has lower reference-peak RMSD, while DriftReact has lower IRC-RMSD and Fréchet error. The paired 95% intervals in Table R11 exclude zero in these respective directions. The results do not support uniform geometric superiority across both datasets. The baseline energy statistics were copied without conversion, and ReacFlow's energy results are unchanged. In manuscript Table 1, ReacFlow retains the lowest reported barrier error on both datasets and the lowest reported per-image energy error on Halo8.
Tables R11–R13 quantify uncertainty using paired bootstrap analysis of the reaction-level errors underlying Tables R10, R4, and R1, respectively. For a target method A and comparator B, define
\bar{\Delta}=\frac{1}{M}\sum_{i=1}^{M}\Delta_i.$$ Negative differences favor A. For each comparison, we draw 10,000 bootstrap resamples, each containing M reaction IDs sampled with replacement. The two methods' saved errors are resampled together for each reaction, preserving their pairing. We compute the mean paired difference in each resample; its 2.5th and 97.5th percentiles define the 95% confidence interval. Transition1x comparisons contain 1,073 evaluation reactions and Halo8 comparisons contain 1,891. All differences and interval bounds below are in Å. The intervals in Tables R11–R13 characterize reaction-level sampling variability conditional on the fixed trained models. **Table R11. Paired-bootstrap comparison of ReacFlow and DriftReact under the common evaluation protocol, based on Table R10.** | Dataset | Metric | DriftReact | ReacFlow | Mean paired difference | 95% CI | | --- | --- | ---: | ---: | ---: | --- | | Transition1x | TS-RMSD | 0.264 | 0.215 | −0.049 | [−0.0576, −0.0407] | | Transition1x | IRC-RMSD | 0.225 | 0.155 | −0.070 | [−0.0769, −0.0632] | | Transition1x | Fréchet | 0.464 | 0.260 | −0.204 | [−0.2175, −0.1908] | | Halo8 | TS-RMSD | 0.188 | 0.175 | −0.013 | [−0.0216, −0.0044] | | Halo8 | IRC-RMSD | 0.125 | 0.165 | +0.040 | [+0.0348, +0.0452] | | Halo8 | Fréchet | 0.216 | 0.280 | +0.064 | [+0.0545, +0.0734] | *Note.* Means reproduce Table R10, which also reports reaction-level SDs. Differences are ReacFlow minus DriftReact; intervals use the paired reaction-level errors from that common evaluation and the bootstrap procedure above. The three Transition1x intervals favor ReacFlow. On Halo8, the TS-RMSD interval favors ReacFlow, while the IRC-RMSD and Fréchet intervals favor DriftReact. The tokenizer contribution is supported separately by the controlled comparisons in Tables R1, R5, and R13. **Changes.** We have described the reporting correction and the shared protocol in Appendix C.1, added the rerun comparison of Table R10 to the appendix, and updated Table 1, its caption and rankings, the abstract, and the corresponding claims in the introduction, Section 4.2, and Appendix C.1, removing the claim of lowest geometry error on both datasets. ## Q2. Endpoint alignment assumptions > “Does the method require a specific relative alignment between the reactant and product structures?” Yes. The model requires atom-mapped endpoints in a common relative coordinate frame, as supplied by the stored benchmark pathways. Preprocessing subtracts the reactant center from the whole path and does not independently align the product before forming $L_k=(1-s_k)R+s_kP$. The benchmark endpoints are the first and last structures of the same stored path, with fixed atom correspondence and a shared coordinate frame. A common rigid transformation preserves their relative placement; moving only the product changes the source interpolation and the model's conditioning. Table R14 reports a separate sensitivity experiment using the archived Full (R+S+C) checkpoint, with inference repeated for each input-placement condition and no weight updates. Its remeasured unperturbed scores agree with the manuscript's Full row when rounded to the manuscript's three decimal places. The checkpoint and replay details are recorded with Table R14. **Measured sensitivity (Table R14).** We evaluated all **1,073 Transition1x reactions** using the archived Full (R+S+C) checkpoint, with no retraining, no reaction filtering, and zero failed outputs in every condition. Product-only rotations of 5°, 15°, and 45° increase all three errors progressively; a 5° rotation changes them by less than 1.5%. At 45°, TS-RMSD, IRC-RMSD, and Fréchet increase by **27.2%, 24.5%, and 23.3%**, respectively; a 0.5 Å product translation increases them by **18.4%, 16.0%, and 15.4%**.
W / Q1. DriftReact reporting and common evaluation
Thank you for pointing out the discrepancy. DriftReact's public benchmark and code provided the basis for our comparison. Our statement that all baseline values were copied directly was inaccurate: we applied an additional normalization conversion to its geometry means and standard deviations when preparing Table 1.
For fixed aligned coordinates, per-atom and per-coordinate RMSD satisfy
dN=3,d3N.
When preparing Table 1, we applied a factor of 3 to the means and standard deviations of all three DriftReact geometry metrics, incorrectly treating them all as per-coordinate (3N) statistics. Inspection of the pinned evaluation implementation confirmed that this conversion was appropriate for the historical TS-RMSD calculation, whereas IRC-RMSD and Fréchet were already normalized per atom (N). We therefore restore the original IRC-RMSD and Fréchet statistics while retaining the converted TS-RMSD. We acknowledge that the original table caption did not clearly disclose this conversion. The remaining baseline geometry entries and all baseline energy statistics were copied without this conversion.
Static inspection of repository commit
67eb280traces the TS evaluation call fromrmsd_coords, throughpymatgen_rmsdandrmsd_core, toKabschMatcher.fit. The locked pymatgen 2025.10.7 implementation averages squared residuals over all N×3 coordinates, giving the historical 3N normalization.In the same pinned release, the separate evaluator for Linear, IDPP, Geodesic, and NeuralNEB uses N-normalized, proper-rotation TS-RMSD through
_kabsch_rmsd, so no additional 3 conversion is applied to those rows. Their TS alignment excludes reflections, whereas the DriftReact TS evaluator also considers mirror matching. These literature-reported results remain distinct from the common-protocol comparison of rerun DriftReact and ReacFlow predictions in Table R10.Table R9. Source values, submitted values, and the reporting correction.
The same factor scales means and SDs. The restored IRC and Fréchet values come directly from the source table. Table R9 records the historical arithmetic correction; Table R10 separately reports predictions generated in our reruns and scored under the shared protocol.
Normalization correction in the DriftReact evaluator. For commit
67eb280with its lockedpymatgen==2025.10.7, the following minimal patch toscripts/evaluate.pyconverts TS-RMSD from 3N to N normalization before aggregating reaction-level means and SDs:The existing valid-atom filtering, reference-peak selection, and TS mirror handling are retained. IRC-RMSD and Fréchet already use N-normalized point distances and receive no additional factor.
Tables prefixed “R” belong to this response; unprefixed table numbers refer to the submission. Geometry errors are in Å, with lower values better.