- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
The authors their EvoState model that predicts physical dynamics by jointly evolving fine, middle, and coarse latent states, then reconstructing physical fields from the fine state using a frozen decoder. Its three-stage framework separates representation learning, dynamics training, and readout.
Critical strengths
-
Promising results with relatively few parameters: The 11.2M-parameter model achieves good long-horizon predictions compared with baseline Walrus-SF models. This suggests a good direction for parameter-efficient physical forecasting.
-
Clear, modular training framework. The paper separates hierarchical representation learning, latent dynamics, and physical readout into three (intuitive) stages. Freezing the encoder and readout during dynamics comparisons helps assess changes in the transition model.
-
A relevant architectural question: Investigating whether coarse latent states should persist across transitions or be recomputed addresses a useful design choice in autoregressive physical modeling that the authors pointed it with ablation.
-
Detailed prediction diagnostics: Beyond aggregate errors, the paper examines individual physical channels, parameter regimes, predicted fields, and spectral behavior.
Critical weaknesses
I write the main weakness that authors may address:
-
Limited distinction from close prior work: HEAP[1] already jointly evolves a hierarchy of latent states which is pretty similar to yours. Given that one of your claim is you novel architecture for spatial connection, I would suggest you clarify your architecture additional contribution and (if possible) provide a comparison with this related approach (otherwise, to me, it will be blurry if your architectural addition is necessary or only marginal).
-
Confounded feedback and supervision changes: The coarse-state ablations that you are proposing change both recurrent feedback and the supervision path, including gradients into Fine. Then I think the the results do not isolate whether the improvement comes from carrying coarse states or from differences in optimization (because the gradient flows back through coarse anyway). Any idea to isolate it?
-
Unequal training exposure and rollout supervision: Walrus-SF receives different training windows size (around 24k), which is fewer than one EvoState epoch. EvoState trains for seven epochs with explicit long-horizon supervision. Comparable long-horizon training is not clearly documented for Walrus-SF. These differences then could explain part of the performance gap. In the current format the outperformance might simply coming from larger seen windows in training.
-
Insufficient architectural ablation and sensitivity analysis: The choices of spatial resolutions, attention-window sizes, encoder depths, and mask tiles require further justification. In particular, comparing number of levels would establish the benefit of the selected hierarchy and its sensitivity to configuration (i.e. why choosing 3 levels and not more/less?).
-
Insufficient justification and transferability analysis of loss weights: The loss components have intuitive motivations, but their relative weights and normalization constants does not have sufficient justification and more importantly sensitivity analysis. The selected hard coded constant weights raise the question weather your model need to be tuned per dataset or not?
Questions for authors
Please see the weaknesses specifically related to HEAP related work and its relation to your work as well as sensitivity analysis.
4 comments
Number of levels and loss weights
W4: Why three levels? Were other design choices tested for sensitivity?
Answer: The three levels are the three stages of the encoder and suffice for the paper's core question; we placed the experiments where they decide that question.
The three levels are the three stages of the Swin V2 encoder (depths 2/4/2, channels 32/64/128). Fine feeds the readout and the coarser levels serve only the dynamics; Middle sits between them, so the coarsest level is not tied directly to the finest. The core question is whether the coarser levels should evolve as state, and our experiments target it: matched comparisons of how the coarser levels are organized, and a second system. The number of levels, per-level resolution, attention window, encoder depth, and mask tile are fixed, and Section 6 states this scope.
W5: Do the loss weights need per-dataset tuning?
Answer: The loss weights do not. Both systems use the same weights, without per-dataset tuning or sweeps; only the training schedule is set per system, and only on Valid.
The revised objective has three weights: 1 for Fine, because the readout uses Fine, and 0.25 each for Middle and Coarse. Both systems share the architecture and these weights; normalization uses per-channel Train statistics, which are computed rather than tuned. The two extra terms of the submitted full model had coefficients fixed before training (ranking 0.1; Persistence-relative 0.5 with ε = 0.05); we dropped them so that all comparisons use one objective, Eq. (5). What differs per system: update counts and batch sizes follow dataset size, the Stage B training horizon follows τ, and on TRL2D the training length, learning-rate schedule, and latent-history noise were chosen on Valid (Appendix B.3). With the same weights, EvoState also holds its accuracy on cooling times held out of transition-model training (Section 5.3).
What this resolves: one set of weights works on two systems whose decorrelation times differ widely and on held-out conditions, which is itself a test of transferability.
Response to Reviewer fAPC: Walrus-SF-140M trained with the same number of windows
Thank you for your thoughtful review and for pointing out the unequal training exposure. We have now completed the experiment that addresses it.
W3: training exposure. Walrus-SF-140M has been trained to its full schedule on the v2 split. It uses the same number of training windows as EvoState (1,084,160), the same official code and one-step-ahead objective as Walrus-SF-12M, and the architecture of the N = 32 model in Figure 1, with 140M parameters, about 12.5 times EvoState's 11.2M. Test was evaluated once at the training endpoint.
Results. Even against a predictor 12.5 times its size, EvoState keeps its advantage once the flow decorrelates. We compare the two along the four dimensions used in the revision: pointwise error, field structure, numerical stability, and cost per step (Section 4). Walrus-SF-140M is more accurate over the first steps and has the lower four-channel mean error in every range. From steps 13–30 onward, however, EvoState has the lower error in most windows (78 of 112 over steps 31–64) and the lower window median in every range (0.299 vs 0.567 over steps 31–64; Table 20). Its tracer error is also lower (Appendix C.4), as is its error on both velocity components over steps 31–64 (Table 14). Its perturbation correlation and amplitude ratio are closer to the truth, which means that its vortices are closer to their true positions and strength. Neither EvoState nor Walrus-SF-140M diverges, and EvoState needs only about 1/32 of the time per step on the same GPU (7.2 vs 229 ms).
Shear-flow v2 Test (112 windows). Mean VRMSE; per-channel columns and the median cover steps 31–64; r and a are window medians at step 64; best per column in bold. Time per step: EvoState 8.1 vs Walrus-SF-12M 15.6 ms; EvoState 7.2 vs Walrus-SF-140M 229 ms on the same RTX 4090.
| Params | Four-channel, steps 13–30 | Four-channel, 31–64 | Four-channel, step 64 | r / a, step 64 | Pressure | Tracer | Velocity x / y | Median | |
|---|---|---|---|---|---|---|---|---|---|
| EvoState | 11.2M | 0.508 | 0.776 | 0.835 | 0.820 / 0.886 | 1.661 | 0.394 | 0.124 / 0.924 | 0.299 |
| Walrus-SF-12M | 12.0M | 0.511 | 1.359 | 2.060 | 0.333 / 1.313 | 2.148 | 0.634 | 0.251 / 2.404 | 0.801 |
| Walrus-SF-140M | 140M | 0.447 | 0.645 | 0.727 | 0.550 / 0.675 | 0.937 | 0.500 | 0.134 / 1.009 | 0.567 |
What the fields show (Appendix C.4). The pressure gap is concentrated in 21 windows in which the true pressure is nearly uniform. VRMSE divides by a near-zero variance there, and these windows account for 81% of EvoState's summed pressure VRMSE. Without them, EvoState has the lower four-channel mean over steps 31–64 (0.340 vs 0.513; Table 14), and in standardized units its pressure RMSE is the lowest of the three models (RMSE 0.027, against 0.051 for Walrus-SF-140M and 0.085 for Walrus-SF-12M). In an example window with structured pressure, EvoState keeps the four low-pressure vortex cores up to step 64, whereas both Walrus-architecture predictors smooth them out (Fig. 11). Walrus-SF-140M does not overestimate the perturbation amplitude as Walrus-SF-12M does (four-channel a at step 64: 0.675 vs 1.313; Table 2). In the Test example window of Fig. 3a, however, it stretches the tracer vortices into filaments, while EvoState matches their number and positions (Fig. 12); over all windows, its tracer r at step 64 is only 0.12. For this reason we report pointwise error throughout but, once predictions decorrelate from the truth, read it together with structure and the fields. Pointwise error mixes errors in position and amplitude (Section 4), and after decorrelation a few windows can dominate its mean.
Exposure and supervision. With the number of windows matched, the main remaining difference in training is the objective: the Walrus-architecture predictors are trained one step ahead (with six history frames, as in the official setup), whereas EvoState is trained on multi-step rollouts; both receive four frames at evaluation. This difference is part of the design being compared (Section 4). The role of the hierarchy itself is tested within EvoState under a single training setup (see our responses to W1 and W2; Section 5.4).
The revised PDF adds these results to Table 2, Section 5.1, and Appendix C.4 (Table 14, Figs. 11–13), with the timing in Table 24 and the unified comparison in Table 20.
We hope this, together with the controls described in our first response, addresses W3. If any concern remains, we would be glad to answer before the discussion closes.
post rebuttal
Thank you for the clarification and efforts you did in your rebuttal.
The concerns in my original queries addressed. The remaining concern is the diversity of your experiment. I can understand that in dynamical systems and PDE community solving simulated systems is common practice, but reviewer v74v concern is also not off. Many approaches test on real word data as well as simulated databases, e.g. ERA5.
Besides, the baseline examples you provided like Poseidon or Walrus, although targeting simulated dataset, but have more diversity including waves, plasma, chemical reaction, etc. instead of restricting to 2 fluid cases.
Thus the generalization of Evostate to even different simulated dynamical systems remains questionable. Please take a look to Well benchmark as an example.
Given this, I give borderline score to the rebuttal version. It is up to AC to weigh toward accept or reject.
Response to Reviewer fAPC : HEAP, carry versus supervision, and fairness
Thank you for the detailed reading, the strengths you list, and the pointer to HEAP. The revision discusses HEAP, adds Walrus-architecture predictors matched in parameters and training windows, separates the organization of the coarser levels from their supervision as you suggested, and adds TRL2D and further generalization tests. W4 and W5 follow in a second comment.
W1: How does EvoState differ from HEAP?
Answer: In what the coarser levels are for. HEAP's decoder reads all levels, so its coarser levels serve both representation and dynamics. EvoState reads out from Fine alone, so Middle and Coarse act only through the dynamics, and their role can be tested with encoder and readout fixed.
Learning the levels. HEAP trains a hierarchical reconstruction autoencoder, then a predictor on its frozen level embeddings. EvoState learns the three levels jointly with a cross-level-aligned same-frame masked-feature (JEPA) objective; each level keeps structure inferable from the same frame, without pixel reconstruction. Section 2 discusses HEAP.
Evidence (shear flow, Section 5.4).
What this shows: the coarser levels act on slow, low-frequency structure. HEAP has no public code and its data are available only on request, so we discuss it rather than reproduce it.
W2: Feedback and supervision changed together. Can they be separated?
Answer: Yes, and the experiments favor carry. On TRL2D we vary write-back and coarser-level supervision separately: with the carried levels supervised, as in EvoState, carry has the lowest error of all five variants at steps 8 and 16 (Table 24, Appendix D.8). On shear flow, replacing the carried coarser levels at inference, with weights and gradients unchanged, raises step-64 error by 113% (Fig. 20): the trained transition relies on the coarser levels it evolved.
Five variants (TRL2D, 24 Valid windows, Table 24). Four-channel mean NRMSE at step 8 / step 16. Within a row only the written-back states differ, which also changes the gradient path into Fine:
What this resolves: with the supervision EvoState uses, carry is the best organization; without coarser-level losses (not EvoState's method), the unsupervised carried states drift.
W3: Training exposure and long-horizon supervision differ. Is the gap unfair?
Answer: With training windows matched, the conclusion stands. Walrus-architecture predictors, trained on a one-step objective, are more accurate over the first steps, and the two are close over steps 13–30; over longer rollouts EvoState stays bounded, runs faster, and keeps amplitude closer to the truth. Each predictor keeps its own objective, so this comparison tests the whole design; the hierarchy is tested inside EvoState (W1). On TRL2D, EvoState trains on rollouts of only four steps yet has lower error from step 6 on and keeps amplitude closer to the truth at step 64, so its long-horizon advantage does not come only from long training rollouts.
Fair comparison. The submitted Walrus-SF models (24,576 windows each) only motivate the question (Section 1). Walrus-SF-12M and Walrus-TRL-12M use Walrus's official code on the same splits, match EvoState in parameters and training windows, and get the same four input frames at evaluation.
What the numbers mean. At step 64 on shear flow, EvoState's error is less than half (0.835 vs 2.060), with divergence 0/112 vs 4/112; at 512 steps it is 1/112 vs 63/112.
Lower error, damped field. In an illustrative TRL2D Test window (t_cool = 0.56, step 12, both trained on all conditions), Walrus-TRL-12M has lower VRMSE (0.180 vs 0.221) but smooths the interface away: amplitude ratio 0.59 vs 1.03, with similar correlation (0.26 vs 0.29). Over steps 4–16 of TRL2D density, Walrus VRMSE is within 1.1× EvoState's in 75 of 117 window-step pairs, and 50 of these are structurally clearly worse (Section 5.2, Appendix C.8).
Speed. 8.1 vs 15.6 ms (shear flow) and 6.7 vs 16.6 ms (TRL2D) per step.