3. Coupling classification and partitioning

Fluid–structure interaction problems are rarely solved as a single, undifferentiated system. Before any mesh is generated or solver is launched, the engineer must decide how the fluid and structural domains will exchange information, when that exchange occurs, and how tightly the two physics are bound together. These decisions define the coupling classification, and they dominate both the stability and the cost of the final simulation. This chapter establishes the three orthogonal axes along which FSI coupling is classified: monolithic versus partitioned solution strategies, one-way versus two-way information exchange, and explicit versus implicit time integration.

Monolithic versus partitioned approaches

In a monolithic (also called fully coupled or simultaneous) approach, the fluid and structural equations are assembled into a single global system and solved together at each time step. The unknowns — fluid velocity, pressure, and structural displacement — are advanced simultaneously. Because the interface kinematics and tractions are enforced within the same linear (or nonlinear) solve, the coupling condition is satisfied to solver tolerance rather than to an iteration tolerance. Monolithic schemes are extremely robust for strongly coupled problems such as incompressible flow past a flexible membrane or a closing heart valve, where the added-mass effect is severe. Their cost, however, is substantial: the global Jacobian is large, poorly conditioned, and requires specialized preconditioners. Off-the-shelf fluid and structural solvers cannot be reused directly; the monolithic system must be built and maintained as a bespoke code.

A partitioned approach keeps the fluid and structural solvers separate. Each solver advances its own domain over a time step, and the two exchange interface data — typically fluid traction to the structure and structural displacement or velocity to the fluid — through a coupling scheme. Partitioned methods dominate industrial practice because they allow mature, validated, and highly optimized single-physics solvers to be coupled with modest glue code. The trade-off is that the interface condition is satisfied only approximately, and for strong added-mass problems the partitioned iteration may diverge unless under-relaxation or a more sophisticated interface quasi-Newton scheme is applied.

One-way versus two-way coupling

One-way coupling means information flows in a single direction. The classic case is a rigid structure or a structure whose deformation is negligible: the fluid exerts pressure and shear on the solid, but the solid does not deform enough to alter the flow field. The fluid solution is computed first, the resulting traction is mapped onto the structural mesh, and a static or transient structural analysis is performed. No feedback loop exists. One-way coupling is appropriate for wind loading on a stiff building, hydrodynamic drag on a rigid submerged body, or thermal stress in a pipe where the wall does not move appreciably.

Two-way coupling means the fluid and structure influence each other continuously. The structural deformation changes the flow domain, which changes the pressure field, which changes the deformation. This feedback is essential for flutter, vortex-induced vibration, parachute inflation, and any problem where the structural displacement is comparable to a characteristic flow length. Two-way coupling is inherently more expensive because the interface must be updated and the coupled system iterated or advanced simultaneously.

The decision between one-way and two-way is not always obvious. A useful diagnostic is the coupling strength parameter, often estimated as the ratio of fluid dynamic pressure to structural stiffness, or more rigorously through a preliminary one-way run: if the maximum structural displacement is less than a few percent of the smallest flow dimension, one-way coupling is likely adequate. If the displacement is larger, or if the flow is separated and sensitive to small geometry changes, two-way coupling should be assumed necessary until proven otherwise.

Explicit versus implicit time integration

The third axis concerns how the coupled system is advanced in time. In an explicit coupling scheme, the fluid and structure are advanced sequentially within a time step without sub-iterating the interface. The fluid solver uses the structural state from the previous time step, and the structural solver uses the fluid load from the previous time step. This is sometimes called a staggered or loosely coupled explicit scheme. It is cheap — one fluid solve and one structural solve per step — but it is only conditionally stable. The stability limit is governed by the added-mass ratio and the time step; for light structures in dense fluids, the explicit scheme can blow up even at very small time steps.

An implicit coupling scheme sub-iterates within each time step until the interface conditions converge. The fluid and structure are solved repeatedly, exchanging updated interface data, until the change in interface displacement and traction falls below a tolerance. This is the partitioned implicit or strongly coupled partitioned approach. It is unconditionally stable for many practical problems and is the workhorse of industrial FSI. The cost per time step is higher, but the allowable time step is much larger, and the solution is far more robust.

It is important not to conflate the coupling scheme with the time integrator inside each solver. A structural solver may use an implicit Newmark scheme internally while the coupling itself is explicit. The classification refers to the interface treatment, not the sub-solver time integration.

How the axes combine in practice

These three classifications are independent, and a real simulation sits at one point on each axis. A typical industrial FSI workflow might be partitioned, two-way, implicit — separate fluid and structural solvers, bidirectional exchange, and sub-iteration to convergence within each time step. A quick scoping study might be partitioned, one-way, explicit — run the fluid, map the load, run the structure once. A research code for a strongly coupled biomedical problem might be monolithic, two-way, implicit.

The most common engineering mistake is to choose explicit coupling for a two-way problem because it is cheaper per step, then discover that the solution diverges as the structure lightens or the flow accelerates. The second most common mistake is to run a one-way analysis on a problem where the deformation is actually large enough to change the flow separation pattern, producing a plausible but physically wrong result. Both errors are avoided by estimating the coupling strength before committing to a scheme.

Interface treatment details that affect the choice

Regardless of the classification, the interface must transfer two quantities: kinematic (displacement or velocity) from structure to fluid, and dynamic (traction or pressure) from fluid to structure. When the fluid and structural meshes are non-matching — which is almost always the case — a conservative interpolation scheme is required. For partitioned implicit coupling, the interface residual is typically defined as the difference between the structural displacement predicted by the fluid load and the displacement actually computed by the structural solver. Convergence is declared when this residual, normalized by a reference displacement, falls below a tolerance such as 1×10⁻⁴.

Under-relaxation is the simplest stabilization: the interface displacement used in the next sub-iteration is a weighted average of the previous and newly computed values. A fixed relaxation factor of 0.5 is a common starting point, but Aitken adaptive relaxation adjusts the factor based on the observed residual history and converges faster. For strongly coupled problems, interface quasi-Newton methods build a low-rank approximation of the interface Jacobian from previous sub-iteration data and apply it as a preconditioner, dramatically reducing the number of sub-iterations required.

Summary of selection criteria

The classification framework presented here is not merely taxonomic. Each choice carries direct consequences for stability, accuracy, and computational cost, and the engineer must justify the selection against the specific physics of the problem. In the chapters that follow, these concepts are applied to concrete solver configurations, interface mapping algorithms, and verification cases that expose the practical differences between the schemes.