- Rating
- 1
- Confidence
- 4
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 1
Read review
Paper summary
The method introduced in this paper aims to leverage task similarity by modeling shared representations across flow regimes and capturing task-specific features through both task vectors and adapters. Task vectors extracted through task-specific fine-tuning are combined into a shared base model, while an adapter is incorporated for each task to further refine its predictions. The premise is that flows at different Reynolds numbers share common underlying physics that can be exploited across tasks. In this case, the authors focus on the 2D incompressible Navier–Stokes equations under varying Reynolds numbers.
Critical strengths
- Broad Baseline Benchmarking: The empirical evaluation includes 13 baselines across three relevant methodological families: general multi-task learning, multi-task PINNs, and model merging. All merging baselines use the same adapter-refinement setup, supporting consistency in this aspect of the comparison.
- Conceptually Interesting Framework for Multi-Regime PDEs: Combining weight-space model merging through task vectors with task-specific adapters is an interesting approach to multi-task PDE modeling. The motivation of sharing information across Reynolds-number tasks while retaining the flexibility to capture task-specific flow features is appealing.
Critical weaknesses
-
Insufficient evidence of predictive accuracy and broader applicability:
- Solution accuracy: The quantitative evaluation relies solely on the weighted PINN test loss, whose interpretation depends on the loss weights and normalization. Relative errors for , alongside a breakdown of the loss components, are needed to assess whether the reported gains correspond to more accurate physical solutions.
- Robustness: Tables 1–7 report no variability across independent training runs. This makes it difficult to assess the robustness of the improvements, particularly in ablations where some differences appear only in the third decimal place.
- Generalization and scope: Evaluation is restricted to one Navier–Stokes setup with six Reynolds numbers, all included in shared training and fusion. Tables 6–7 test reuse across these known tasks and show substantially larger off-diagonal losses; they do not establish adaptation to unseen regimes. A held-out- evaluation would address this gap, while additional PDEs or more diverse Navier–Stokes configurations would strengthen the evidence for broader applicability.
-
Insufficient experimental specification and reproducibility:
- Dataset and temporal evolution: The simulation conditions and temporal evaluation protocol are insufficiently specified. Figure 3 shows individual snapshots without identifying their times or how far the flows have evolved from their initial conditions. The initial conditions, simulation time horizon, and training/test time ranges are needed to interpret the regime-dependent dynamics and determine whether evaluation measures temporal interpolation or extrapolation.
- Data and sampling: The manuscript does not report the spatial and temporal resolutions or the numbers of interior collocation points, boundary points, and observation points used in training and evaluation.
- Baseline comparisons: The architectures, learning rates, optimizer settings, and tuning budgets for the 13 baselines are insufficiently documented, making it difficult to assess whether comparisons use comparable computational budgets.
(Minor Remark)
- Section 3.4 - The paper is generally well written, but SharedMLP and HeadMLP are introduced without sufficient definition. Although the residual bottleneck adapter and its placement between these components are described, defining the network components and showing them in the architecture diagram would improve clarity.
- Figure 1 - Figure 1 is a bit confusing, what MLT strategy is being used, is c) normalized wrt the best score, or why is it that for c, it has the same performance in all regiemes.
- Pre-training cost vs Online cost - this would give the author a better assessment of the trade-off.
Questions for authors
- Dataset and temporal evolution: What initial conditions, boundary conditions, forcing, spatial resolution, and simulation time horizon define the six Reynolds-number tasks? At what times are the Figure 3 snapshots taken, and how far have the flows evolved from their initial conditions? Are the initial conditions shared across Reynolds numbers? Do the reported test losses cover multiple time steps or only the snapshots shown in Figure 3? What time ranges are used for training and testing? Specifically, does evaluation test temporal interpolation (e.g., training on samples spanning and testing at unseen times within that interval) or temporal extrapolation (e.g., testing at )?
- Solution accuracy and variability: Can the authors report relative errors for , alongside the individual test-loss components and their weights? How consistent are the reported improvements across independent training runs?
- Contribution and implementation of model fusion: Table 2 shows that MF-PINN outperforms the “w/o Fusion” variant. How is this variant constructed? In particular, are adapters trained directly on the pretrained model, using the same adapter architecture, initialization procedure, and training budget as the full method? Additionally, Figure 2 describes the fusion coefficients as learnable. At which stage and using what objective are they optimized? Section 3.4 specifies that only adapter parameters are updated during refinement, while Algorithm 1 does not include a coefficient-learning step.
- Parameter savings and computational cost: How are the parameter counts in Table 5 calculated for each model and adapter, and which adapter bottleneck dimension is used? Please report wall-clock time and hardware for shared pretraining, full task-specific fine-tuning, adapter initialization/refinement, and inference, including the total training cost across all six tasks, so that the accuracy–storage–compute trade-off can be assessed.
- Applicability to unseen regimes: Can the method adapt to a Reynolds number excluded from shared pretraining and task-vector construction? What additional training and target-task data would be required, and are supporting results available? The current cross-task tables evaluate regimes already included in training and therefore do not establish this capability.