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

Physics guides

RunMat studies use one geometry, one solver mesh, a physical model, and an analysis graph. The physics block inside each analysis declaration states the equation family and procedure; it does not silently supply materials, references, boundary conditions, damping, or initial state.

Choose the guide that matches the question you need to answer. Together these pages document every physics family exposed by the language, every currently named procedure, the actual admitted numerical realization (or its absence), required model data, fields/state, validation checks, and common failure modes.

StudyGuideTyped .fea contractNative .fea execution
Stress, deformation, modes, vibration, or bucklingStructural analysisAvailableAvailable
Steady or transient temperatureHeat transferAvailableNot yet connected end to end
Electric or magnetic fieldsElectromagneticsAvailableNot yet connected end to end
Board trace impedance, delay and couplingTrace impedanceAvailableAvailable
Pressure modes or sound propagationAcousticsAvailableNot yet connected end to end
Incompressible flowFluid flowAvailableNot yet connected end to end
Temperature-dependent deformationThermomechanical analysisAvailableNot yet connected end to end
Joule heating and temperatureElectrothermal analysisAvailableNot yet connected end to end
Flow with heat transferConjugate heat transferAvailableNot yet connected end to end
Two-way fluid and structural motionFluid–structure interactionAvailableNot yet connected end to end

“Typed contract available” means the parser and checker understand the family, its quantities, conditions, independent domain, and state types. It does not mean that the public executor can run that family today. runmat check validates source; runmat run is the execution boundary. See Current status for the qualification matrix.

All guides use the same workflow: inspect or construct geometry, name stable regions, assign materials to solid/cell regions, declare conditions on regions with compatible topology, define one or more analyses, then request typed outputs. Placement and worker policy are separate from physics, so moving a qualified study to a cluster cannot change its equations.

Which procedures can I declare in a .fea file?

FamilyProcedures understood by the checkerCurrently registered low-level realization
Structuralstatic, preload, modal, transient, modal transient, harmonic, modal harmonic, prestressed modal, buckling, prestressed harmonic, modal response spectrum, random response, nonlinearMultiple structural realizations; public typed executor is structural-only
Thermalsteady, transientTet4/Tet10 Galerkin conduction; steady linear and backward-Euler transient
Electromagneticstatic, transient, harmonic, nonlinearReduced edge-graph curl–curl harmonic only
Acousticstatic, modal, transient, harmonic, nonlinearReduced Helmholtz graph
Fluidsteady, transient, harmonic, nonlinearReduced channel steady/transient only
Thermomechanicalsteady, transient, nonlinearOne-pass prescribed-temperature structural response
Electrothermalsteady, transient, nonlinearNone
Conjugate heat transfersteady, transient, nonlinearReduced partitioned flow/thermal transfer
Fluid–structure interactionsteady, transient, nonlinearReduced partitioned relaxation

The checker accepts the generic static/steady, transient, harmonic, and nonlinear shapes where the family contract exposes them. A registered low-level realization is still not a public typed execution path. Admission requires an exact family, procedure, topology, source projection, boundary transfer, coupling, and backend match.

How does RunMat keep physics and execution separate?

A procedure compiles into typed physical state and operators. An execution policy selects eligible placement, workers, accelerator requirements, resilience, and publication; it cannot change the governing equation or substitute a reduced formulation. Result evidence records the chosen spatial, constitutive, temporal, recovery, source, topology, boundary-transfer, and coupling implementations. If no registered realization satisfies the study's formulation requirement, execution fails closed.

Shared references

  • Write and run an FEA study
  • FEA language
  • Geometry and region selection
  • Meshing
  • Constraints
  • Loads and excitations
  • Verification and validation
On this page
  • Which procedures can I declare in a .fea file?
  • How does RunMat keep physics and execution separate?
  • Shared references