The core difficulty
Multiphysics is rarely hard because the individual physics is hard. It is hard because of what happens at the interface — transferring data between non-matching meshes without losing conservation, and coupling schemes that go unstable for reasons that have nothing to do with your timestep.
Teams approaching coupled simulation for the first time usually budget for the physics and are surprised by the interface. This is where the engineering effort actually concentrates.
The two coupling architectures
| Monolithic | Partitioned | |
|---|---|---|
| Structure | One combined system | Separate solvers exchanging data |
| Stability | Robust | Can diverge in strong coupling |
| Reuse existing codes | No | Yes — the main attraction |
| Linear system | Large, badly conditioned | Two well-behaved systems |
| Implementation effort | High | Lower to start, higher to stabilise |
| Typical use | Strongly coupled problems | Most industrial FSI and CHT |
Most practical multiphysics is partitioned, because reusing a validated fluid solver and a validated structural solver is enormously cheaper than writing a combined one. The cost of that choice is stability work.
Why partitioned schemes diverge
The classic failure is the added-mass effect in fluid-structure interaction.
- The fluid solver computes pressure on the structure.
- The structure deflects under that load.
- The deflection changes the fluid domain, so pressure changes.
- If the fluid the structure must accelerate is comparable to the structure's own mass, the response over-predicts.
- Each exchange amplifies the error, and the simulation diverges.
The counterintuitive part: reducing the timestep makes this worse, not better. Added-mass instability is a property of the coupling scheme, not of temporal resolution. Teams who assume it is a timestep problem can lose weeks before finding the real cause.
The mitigations are specific: under-relaxation of the exchanged quantity, Aitken dynamic relaxation that adapts the factor automatically, or implicit (strongly coupled) schemes that sub-iterate to convergence within each timestep.
Data transfer across non-matching meshes
The fluid mesh and the structural mesh almost never share nodes at the interface. The fluid wants a fine boundary layer; the structure wants elements sized for bending. So every exchange requires interpolation.
- Loads must be conservative. The total force transferred to the structure must equal the total force computed by the fluid. Naive point interpolation loses some, and the error accumulates over a long transient.
- Displacements must be smooth. Interpolated motion with kinks produces poor mesh quality on the fluid side.
- Curved interfaces need care. Nearest-neighbour mapping on a curved surface introduces geometric error.
- Common approaches include consistent interpolation, radial basis functions, and mortar methods — each trading accuracy against cost and implementation complexity.
If your coupled simulation slowly loses energy or mass over a long run, suspect the interface transfer before suspecting the physics.
Mesh motion — the underestimated piece
When the structure deflects, the fluid mesh must follow. That is its own engineering problem:
- Mesh deformation — moving interior nodes smoothly so quality degrades gracefully. Spring analogy or linear elasticity methods are common.
- Quality monitoring — detecting when cells become too skewed to trust.
- Remeshing — regenerating when deformation is large, which introduces interpolation error of its own.
- ALE formulation — the fluid equations must account for a moving mesh, or conservation is violated.
Common coupled problems, ranked by difficulty
| Problem | Coupling strength | Main difficulty |
|---|---|---|
| Conjugate heat transfer | Weak to moderate | Interface temperature/flux matching |
| Thermal-structural | Usually one-way | Often simplest coupled case |
| FSI, stiff structure in gas | Weak | Manageable with under-relaxation |
| FSI, flexible structure in liquid | Strong | Added mass; needs implicit coupling |
| Electro-thermal-fluid | Varies | Three-way exchange bookkeeping |
| Reacting flow with radiation | Strong | Stiff source terms plus coupling |
Check whether you actually need two-way coupling. A great many industrial problems are adequately captured one-way — compute the fluid loads, apply them to the structure, done. If the structural deflection does not meaningfully change the flow, two-way coupling adds cost and instability risk for no benefit.
Validating a coupled solver
Validation is harder than for single physics, because errors can originate in either solver or in the interface:
- Validate each solver independently first, against its own benchmarks. Never debug coupling with an unvalidated component.
- Test the interface in isolation — transfer a known field and confirm conservation and accuracy.
- Use established coupled benchmarks with published reference results.
- Monitor conserved quantities over long runs; drift reveals interface problems.
- Check coupling convergence per timestep, not just overall residuals.
Scoping a coupled simulation capability? Tell us which physics must talk to which — the coupling strength usually determines the architecture. See our CFD solver service and FVM vs FEM.