- Rating
- 3
- Confidence
- 2
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 3
Read review
Paper summary
The paper studies how to improve the rollout stability of neural operators on Stefan phase-change problems with sharp moving interfaces. The authors propose XENO, using U-Net to predict a interface field and OEB to add corrections to neural operator. Experiments show substantially reduced rollout interface errors in the sharp R4 regime compared with baselines including FNO and Transolver.
Critical strengths
- The problem is clearly motivated and the method is effective in the target regime. The paper provides detailed analysis about the phenomenon and experiments about the method.
- The evaluation covers diverse baselines and includes informative ablations and scope analyses. Results on additional regimes, together with failure rates and computational costs, clarify the method’s benefits and limitations.
Critical weaknesses
- The mechanism is not fully explained. The spectral measurements and ablations support the effectiveness of interface-conditioned enrichment, but do not establish what drives error amplification during rollout or how OEB suppresses it.
- The evidence for broader applicability is limited. The largest gains are concentrated in the R4 Stefan regime, while improvements are small or absent in other equations. It would be helpful to know whether the improvement extends to other interface problems, or how to identify problems where XENO is beneficial.
Questions for authors
- The paper describes the R4 failure as heterogeneity-driven, but R3 and R4 differ in several factors at once, including material heterogeneity, interface sharpness and boundary conditions. The Allen–Cahn sweep is also confounded by its restoring reaction term. Could you vary one factor at a time, to identify which property of R4 causes the baselines to diverge?
- What evidence explains how OEB changes error propagation during rollout in R4? Could you track the evolution of a small, physically consistent interface perturbation under FNO and XENO in both R3 and R4?
- Beyond the regimes already evaluated, do the results suggest measurable characteristics that could identify other problems likely to benefit from XENO? How might the findings guide its use in a new physical setting?
3 comments
This comment addresses: Question Q1.
Regarding Q1: "R3 and R4 differ in several factors at once ... Could you vary one factor at a time?"
We varied one factor at a time on R4.
Material information (full data). Giving FNO the exact material layout drops its 20-step error from 30.66 to 2.00 px. Giving XENO the same layout also helps (1.00 → 0.21 px). XENO stays ahead on moving fronts (0.79 vs 12.90 px) and at 100 steps (19.84 vs 30.85 px). Details in Reviewer: mXQd-Q1.
One-factor R4 variants. We regenerated R4 changing one factor at a time and kept everything else the same: (a) uniform material (same diffusivity everywhere); (b) mushy band twice as wide (a wider melting range); (c) constant ambient temperature (no time-varying boundary forcing). These are separate, lower-data experiments. Their original-R4 numbers should not be compared with the full-data results above. FNO and XENO were trained from scratch for each, with the same protocol, on 100 train, 50 validation and 50 test trajectories. This is the size that fit the discussion period. Median px on the 50 test trajectories:
| condition | FNO 20 / 100 steps | XENO 20 / 100 steps |
|---|---|---|
| original R4 | 23.68 / 149.55 | 22.16 / 24.42 |
| uniform material | 24.32 / 28.50 | 18.39 / 45.18 |
| mushy band ×2 | 26.73 / 119.86 | 24.27 / 27.27 |
| constant ambient | 59.42 / 150.26 | 22.06 / 31.83 |
With 1/16 of the training data, neither model gets below 5 px in any condition, including the original. Within that limit:
- No single change makes FNO stable at 20 steps.
- XENO has lower 20-step error than FNO in all four conditions (per-case: 41/50 original, 48/50 uniform).
- At 100 steps FNO blows up (about 120–150 px) on original, mushy and constant-ambient. XENO stays at 24–32 px. With uniform material FNO does not blow up (28.50 px), while XENO reaches 45.18 px.
Limits: (b) also changes the latent-heat release, so it is not a pure sharpness change. Run-to-run variation at this data size is large. In (c) only 13 of 50 test trajectories had time-varying forcing, yet FNO's error also changed (23.44 → 73.27 px) on the 37 where the change does nothing. So these small runs say more about which model is better within a condition than about differences between conditions.
Conclusion: the full-data material-input experiment shows that giving FNO the material layout greatly reduces its 20-step error. This suggests that missing material information contributes substantially to its failure. Our smaller experiments do not establish how much each factor contributes on its own.
Planned revision: Section 4.2 names all three factors and reports both controls. Section 6 states that a full-data one-factor study is not done.
Resolution: we tested material layout, mushy-band width and boundary forcing separately. No single factor explains the results conclusively. The full-data material-input experiment shows that material information matters. XENO has lower 20-step error than FNO in all four small-data conditions, and also when both get the material layout.
This comment addresses: Weakness W2 and Question Q3.
Regarding W2: "... how to identify problems where XENO is beneficial." and regarding Q3 "Do the results suggest measurable characteristics that could identify other problems likely to benefit from XENO?"
Our observations suggest two checks that can be run before training XENO. They are based on four regimes and are not validated general rules:
- One-step vs 20-step error of a plain FNO. On R4 it jumps (below 0.2 px at one step, 30.66 px at 20). On R3 and Burgers it does not.
- The perturbation test (Q2). If a plain FNO grows a 1-px interface perturbation, enrichment is likely to help. FNO grows it 19× on R4 (to 26.75 px). In the perturbation test, FNO ends at 2.36 px on R3, with no large growth. Separately, in the R3 accuracy results, XENO is only slightly better than FNO (1.6 vs 1.8 px), while Transolver reaches 1.0 px (Table 1).
Both need only one trained FNO.
Separately, after training, the learned gate of XENO can be inspected. It is not a pre-training test. The gate |g_E| (Appendix N) is 0.001 on R1 (1D Stefan with exact solution), 0.00 on Burgers, 0.68 on R3, 0.38 on Allen–Cahn and 1.94 on R4. It was highest where XENO helped most.
In our four regimes, XENO helped most when a plain FNO's error starts at a sharp moving interface and grows during rollout. Where the interface is wide or the plain model is already stable, the gain was small, or XENO was worse (Burgers: 3.0 vs 0.8 px for FNO).
Planned revision: Section 6 gives these checks as a guide for new problems.
Resolution: two pre-training checks (a plain FNO's one-step vs 20-step error gap, and its growth of a 1-px interface perturbation) and one post-training signal (XENO's gate). Both pre-training checks indicate potential benefit on R4, where the gain is large, and the post-training gate is also largest on R4. On R3, Burgers and Allen–Cahn the signals are weaker and the gain is small or negative. These are preliminary observations from four regimes.
We hope these answers address your questions on the mechanism, the R4 factors and applicability. Thank you again for the constructive suggestions. We are happy to clarify anything further during the discussion.
This comment addresses: Weakness W1 and Question Q2.
Thank you for the thoughtful review and the constructive questions. Your suggestions to track a perturbation and to vary one factor at a time were concrete enough that we could run both during the discussion period. The results are below.
Where each point is answered:
Regarding W1: "... do not establish what drives error amplification during rollout or how OEB suppresses it." and regarding Q2: "Could you track the evolution of a small, physically consistent interface perturbation under FNO and XENO in both R3 and R4?"
We ran this experiment. We grew the liquid region of the initial state by 1 px. In the new liquid cells we set T to the melting temperature and H from the trajectory's enthalpy relation, so the state stays physically consistent. Then we rolled out the original and perturbed states with the same model (50 test trajectories per regime). Median distance between the two predicted interfaces (px):
On R4, FNO grows a 1-px perturbation about 19× in 20 steps. XENO keeps it at its starting size. On R3, neither model shows the large growth seen for FNO on R4. The final separation is 2.36 px for FNO and 2.28 px for XENO, compared with 26.75 px for FNO on R4. This shows that the perturbation behaves differently under FNO and XENO. It does not isolate which part of OEB causes the difference, or explain why R4 produces the growth (see Q1).
A possible explanation, consistent with but not proven by these numbers: in FNO, a local error at the interface spreads into all Fourier modes and across the domain. On R4, where the temperature field has much sharper features (99th-percentile |∇T| 15× larger than on R3), this spread error grows step by step. XENO's enrichment acts near the predicted interface, so it can correct the error locally. This agrees with the spectral result in Appendix A: FNO's high-frequency error share rises during rollout on R4, but not on R3 and not for XENO.
Planned revision: a new subsection in Section 4 with this table and a figure. The spectral results (Section 4.3, Appendix A) are given as supporting evidence.
Resolution: on R4, a small, physically consistent interface perturbation grows 19× in 20 steps under FNO and does not grow under XENO. On R3 both end near 2.3 px, with no large growth. What drives the growth within R4 is in Q1.