- Rating
- 2
- Confidence
- 3
- Informativeness
- 1
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
The paper proposes a compact conditional neural-field architecture for PDE surrogate modelling. A task-specific encoder (a graph message-passing encoder with node-to-token attention for meshes, or a multiscale CNN for structured grids) produces a per-node context H and a pooled global code z. A coordinate-conditioned iterative decoder uses both, with FiLM modulation from [z, h_i]. Repeated affine maps (message, token and decoder maps) share one base matrix across depth and add a per-step rank-4 LoRA-style update (as in Relaxed Recursive Transformers), to reduce parameter count.
Critical strengths
- The models are competitive at under 1M parameters. Reaching errors in the same range as Transolver on Elasticity/Airfoil/Pipe/Darcy with roughly a third to half of the parameters is a useful data point for practitioners who care about storage.
Critical weaknesses
-
The evaluation protocol does not support the accuracy-size claims. The headline numbers are validation errors of checkpoints selected on that same validation set. They are then placed next to published test-set results of baselines in Table 1. This is optimistically biased. According to the appendix, for Darcy a test split exists (rows [0,200) of the second source) but is not reported. Where true holdouts are used (ShapeNetCar, AirfRANS), the model is worse than Transolver: velocity +21%, drag +56% on ShapeNetCar; AirfRANS drag error 2.65 with Spearman 0.50.
-
The contribution is thin, and the paper's own ablations undercut the main design. (a) Pn Elasticity the independent-map model is 24.8% more accurate. The adapted model saves parameters but costs accuracy, and there is no parameter-matched comparison to show that sharing+LoRA is a better use of a parameter budget than simply shrinking the network. (b) Replacing the sample-dependent z with a learned constant even slightly helps, in every configuration that is actually used (token-enabled Elasticity, Airfoil CNN, ShapeNetCar). z only matters in a token-disabled configuration that is never deployed. So the "conditional" part of the title is not supported as a useful design choice.
Questions for authors
Q1. Can the authors report test-split results for all static tasks, at least Darcy where a test split exists, with checkpoints selected only on validation data?
Q2. Can the authors run Transolver with the same reference-geometry / correspondence inputs used by your Elasticity and Airfoil adapters, so the benefit of the architecture can be separated from the benefit of the extra inputs?