RunMat
  • Pricing
RunMat
GitHub
GitHub
Sign inTry in browser
DesktopRuntimePhysicsCADAdministrationAgent

Get RunMat updates

New releases, guides and examples.

Product+
  • Runtime
  • GPU
  • Parallel
  • Compile
  • Interop and MEX
  • Simulation
  • MCAD
  • ECAD
  • Enterprise
  • AI integrations
  • Pricing
  • Download
Math+
  • Signal processing
  • Linear algebra
  • Statistics
  • Curve fitting
  • Differential equations
  • Control systems
  • Optimization
  • Finance
  • Data and tables
  • Plotting
Physics+
  • Simulation overview
  • Structural
  • Thermal
  • Electromagnetic
  • Joule heating
  • Thermal stress
  • Acoustics
  • Fluid flow
  • Conjugate heat transfer
  • Fluid–structure
  • What is FEA
Industries+
  • Aerospace
  • Automotive and transportation
  • Defense
  • Electronics and semiconductors
  • Energy
  • Industrial machinery
  • Life sciences
  • Quantitative finance
Learn+
  • Guides
  • Docs
  • Function reference
  • Language reference
  • Migration guide
  • Changelog
  • MATLAB Online
  • MATLAB AI agent
  • For students
Compare+
  • RunMat vs MATLAB
  • RunMat vs Ansys
  • RunMat vs SOLIDWORKS
  • RunMat vs Altium
  • RunMat vs Cadence
  • RunMat vs COMSOL
  • RunMat vs Python
  • RunMat vs Julia
  • RunMat vs Physics AI
  • RunMat vs Octave
  • Benchmarks
  • MATLAB alternatives
  • All comparisons
Company+
  • About
  • Blog
  • Contact
  • Source code↗
  • License
  • Privacy
  • Terms

Product

  • Runtime
  • GPU
  • Parallel
  • Compile
  • Interop and MEX
  • Simulation
  • MCAD
  • ECAD
  • Enterprise
  • AI integrations
  • Pricing
  • Download

Math

  • Signal processing
  • Linear algebra
  • Statistics
  • Curve fitting
  • Differential equations
  • Control systems
  • Optimization
  • Finance
  • Data and tables
  • Plotting

Physics

  • Simulation overview
  • Structural
  • Thermal
  • Electromagnetic
  • Joule heating
  • Thermal stress
  • Acoustics
  • Fluid flow
  • Conjugate heat transfer
  • Fluid–structure
  • What is FEA

Industries

  • Aerospace
  • Automotive and transportation
  • Defense
  • Electronics and semiconductors
  • Energy
  • Industrial machinery
  • Life sciences
  • Quantitative finance

Learn

  • Guides
  • Docs
  • Function reference
  • Language reference
  • Migration guide
  • Changelog
  • MATLAB Online
  • MATLAB AI agent
  • For students

Compare

  • RunMat vs MATLAB
  • RunMat vs Ansys
  • RunMat vs SOLIDWORKS
  • RunMat vs Altium
  • RunMat vs Cadence
  • RunMat vs COMSOL
  • RunMat vs Python
  • RunMat vs Julia
  • RunMat vs Physics AI
  • RunMat vs Octave
  • Benchmarks
  • MATLAB alternatives
  • All comparisons

Company

  • About
  • Blog
  • Contact
  • Source code↗
  • License
  • Privacy
  • Terms
GitHubXLinkedIn

© Dystr, Inc. · RunMat v0.7.1, Nov 17, 2026

RunMat® is a registered trademark of Dystr, Inc. MATLAB® is a registered trademark of The MathWorks, Inc. RunMat is not affiliated with, endorsed by, or sponsored by The MathWorks, Inc.

/
    • Overview
    • Structural
    • Thermal
    • Electromagnetic
    • Trace impedance
    • Acoustics
    • Fluid flow
    • Thermal stress
    • Joule heating
    • Conjugate heat transfer
    • Fluid–structure
Docs>Physics>Physics

Fluid–structure

Fluid–structure interaction (FSI) transfers fluid traction to a structure and structural wall motion back to the fluid. The paired interface is explicit; matching-looking CAD faces do not create coupling.

runmat run executes steady and transient fluid–structure studies. The fluid side is the canonical finite-volume flow of the fluid flow analysis on the deformed fluid domain; the structure is a small-strain linear elastic solid on the solid regions of the same conformal mesh. The two sides are iterated to agreement in every solve or time interval.

What interface equations does FSI enforce?

At a no-slip fluid–structure interface Γfs\Gamma_{fs}Γfs​, the continuum conditions are

uf=d˙s,σfnf+σsns=0.\mathbf u_f=\dot{\mathbf d}_s, \qquad \boldsymbol\sigma_f\mathbf n_f +\boldsymbol\sigma_s\mathbf n_s=\mathbf0.uf​=d˙s​,σf​nf​+σs​ns​=0.

RunMat applies them as follows:

  • Traction to the structure. The pressure and viscous force of every wetted finite-volume face, negated, is shared between the face's structural nodes by its consistent shape-function weights. The structure receives exactly the force the wall exerts on the fluid.
  • Motion to the fluid. The fluid interior follows the wall through a volume-weighted Laplace extension of the interface displacement, and the flow is solved on that deformed domain. In a transient study every face sweeps an exactly integrated volume between configurations, so cell volume changes satisfy the geometric conservation law, and the wetted wall moves with the structure's velocity while carrying exactly its swept flux.
  • Agreement. Each coupling iteration solves the flow, loads and solves the structure, and relaxes the interface displacement with Aitken's dynamic factor. Iteration stops when the structure's response to the flow reproduces the displacement that shaped it, to the coupling tolerance.

Which FSI procedures are defined?

ProcedureContractExecution
fluid_structure_interaction steadyEquilibrium deflection under steady flow and the flow through the deflected passageRuns from runmat run
fluid_structure_interaction transientMoving-mesh backward-Euler flow and average-acceleration Newmark structure, converged every intervalRuns from runmat run
fluid_structure_interaction nonlinearLoad-factor domainTyped contract; not yet executed

How do I declare an FSI interface?

model flexible_wall {
    assign material.water to geometry.duct.region.water
    assign material.rubber to geometry.duct.region.wall
    constraint inflow {
        fluid.velocity { target = geometry.duct.region.inlet; value = [0.01 m/s, 0 m/s, 0 m/s] }
    }
    load outflow {
        fluid.outlet_pressure { target = geometry.duct.region.outlet; value = 0 Pa }
    }
    constraint mounted {
        structural.fixed { target = geometry.duct.region.mount }
    }
    interface coupled_wall {
        fluid_structure.no_slip {
            primary = geometry.duct.region.fluid_wall
            secondary = geometry.duct.region.structural_wall
        }
    }
}

study flexible_duct {
    geometry = geometry.duct
    mesh = mesh.duct
    model = model.flexible_wall
    analysis response {
        fluid_structure_interaction transient {
            start_time = 0 s
            end_time = 1 s
            time_step = 1 ms
        }
    }
    output wall_displacement = analysis.response.field.node.displacement
    output pressure = analysis.response.field.cell.fluid_pressure
}

The declared interface is the fluid's wall: it imposes no slip relative to the moving structure, so the fluid needs no separate wall law there. Every face where the fluid meets the structure must belong to a declared interface. The structure needs a fixed support (structural.fixed); axis- aligned symmetry planes (structural.symmetry) are also admitted.

What does an FSI run publish?

  • field.node.displacement: structural displacement on the solid and the mesh motion of the fluid, on every node of the reference mesh.
  • field.cell.fluid_velocity and field.cell.fluid_pressure on the deformed fluid domain, in the reference cell order.
  • Interface evidence: every coupling iteration's displacement residual, the resultant fluid force on the structure, the work of the interface traction and the structural strain energy (a linear structure loaded at the interface stores half of that work in a steady study), and the equilibrium residuals of the structure and the mesh motion. A transient study reports, for every accepted interval, its coupling iterations and residual, the cumulative interface work, the strain and kinetic energy (average acceleration makes their sum equal the work), and the structure's dynamic residual.
  • field.element.stress and field.element.von_mises_stress on the solid, recovered from the converged displacement: Not yet releasedStatus.

A one-way study, where a structural analysis takes the pressure and wall shear stress of an earlier fluid analysis as a load on the wetted faces without feeding the deflection back into the flow, is Not yet releasedStatus.

How do I choose coupling time step and convergence tolerance?

The time step must resolve both fluid transport and structural dynamics. Added-mass-dominated cases (a light wall in a dense fluid) couple strongly and need more coupling iterations per step; Aitken relaxation adapts the factor each iteration. The structure is small-strain: large rotations are outside the envelope.

See fluid flow, structural analysis, fluid constraints, structural constraints, interfaces, and current status.

On this page
  • What interface equations does FSI enforce?
  • Which FSI procedures are defined?
  • How do I declare an FSI interface?
  • What does an FSI run publish?
  • How do I choose coupling time step and convergence tolerance?