Structured Simulators and Neural Operators › Choosing the Right Structure

Michael BrenndoerferJune 22, 20263 min read
World Models HandbookAll chapters
Part 4 of 12Space, Physics, and Causality
Chapter 22Structured Simulators and Neural Operators › Choosing the Right Structure
Reading section 8 of 11 · Choosing the Right Structure · 3 minSection 8 of 11 · 3 min

Book contents

Section 8 of 11 · 3 min read

Structured Simulators and Neural Operators › Choosing the Right StructureOne section · Sections in this chapter8 / 11 ↓
Reading tools Definitions & inline links

Choose your expertise level to adjust how many terms are explained. Beginners see more tooltips, experts see fewer to maintain reading flow. Hover over underlined terms for instant definitions.

Article links

Make inline references clickable

The four families form a design spectrum, and the choice among them is driven by what you know, what you have, and what the model is for. Reading the table by columns is instructive: the "hand-designed" column generally shrinks as you move down, while the "sweet spot" column tracks how much physics you can commit to in advance. The data-hunger labels are qualitative heuristics, not controlled cross-family measurements; they depend on the task, target error, architecture, data quality, and evaluation regime.

The four families of structured world models, arranged from most hand-designed physics to most learned.
FamilyWhat is hand-designedWhat is learnedData hungerSweet spot
Differentiable simulatorEquations, integratorParameters, plans, residualsVery lowKnown physics, unknown constants, control
Graph-based modelsLocality, pairwise sums, integratorInteraction lawsLow to moderateMany interacting objects or particles
Neural ODEsIntegrator, state dimensionFull vector fieldModerateSmooth continuous-time processes, irregular data
Operator learningFunction-space architectureSolution operatorModerate to highFields and PDEs, multi-resolution deployment

A few rules of thumb distilled from the chapter:

  • Differentiate what you know, learn what you do not. If the equations are right up to parameters, use a differentiable simulator and fit the parameters. If only the interaction structure is known, learn inside a graph model. Reserve learning capacity for unknown components. Every valid equation you supply is one less relation the data must identify.
  • Match the architecture's bias to the physics' structure. Pairwise locality calls for graphs, temporal smoothness calls for differential equations, and spatial nonlocality calls for operators. A mismatched bias can waste capacity or exclude the target dependency entirely, as the pointwise heat baseline demonstrates.
  • Prefer hypothesis classes that contain the target dependency structure and can approximate the dynamics to the fidelity the task requires. The pointwise MLP failed the heat equation not for lack of width but because it had no pathway for cross-location dependence. Extra width cannot repair a missing dependency pathway.
  • Hybrid physics-plus-residual models are useful when core physics is trustworthy and systematic residual effects are learnable. Physics-informed neural networks likewise add differential-equation residuals and boundary or initial-condition information to the objective, although some variants enforce conditions directly. A persistent, validated residual can flag where a mechanistic model disagrees with data, but attributing it to missing physics requires ruling out observation noise, state-estimation bias, discretization error, parameter error, distribution shift, and failed optimization.