SHD Sim Multiphysics
Conjugate heat transfer (partitioned)
Only when the solid needs a real structural solver; chtMultiRegionFoam otherwise
preCICE
In development.
What it is
Fluid and solid in separate solvers, exchanging temperature and flux at the interface. Worth doing only when the solid side needs a real structural code, for phase change, plasticity or a constitutive model a CFD solver does not carry. Otherwise chtMultiRegionFoam does the same job in one solver, better.
What this analysis needs from you
- Both solvers configured, plus preCICE between them
- Interface meshes that map cleanly
- A good reason not to use chtMultiRegionFoam, which is the default answer
Typical uses
- Thermal-mechanical assessment needing a structural solver on the solid
- Cases where solid behaviour is nonlinear
- Reusing an existing validated structural model rather than rebuilding it
- Coupling across organisations that own different halves
Industries
Sectors where this analysis is routinely asked for.
- Nuclear & energy
- Aerospace
- Multi-team programmes
- Research & academia
What comes out
- Coupled thermal fields across two solvers
- Interface temperature and flux history
- Iteration convergence record
- Reuse of an existing structural model
Backend
preCICE
Chosen for this analysis type, with its capability verified against the module plan — not decided later.
Status
Phase 4 — one-way mapping comes well before two-way. Telling us you need this analysis moves it up the order — modules are sequenced by who is waiting for them.