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.

/
    • Grammar
    • Declarations
    • Procedures
    • Types, units and expressions
    • Files, modules and imports
    • Studies, analyses and state
    • Outputs, fields and observations
    • Operations and output queries
    • Operation reference
    • RunMat function integration
    • Diagnostics and tooling
    • Geometry features and AP242
    • Geometry, models and assignments
    • Constraints, loads and interfaces
    • Fluid materials
Docs>Physics>Language reference

Files, modules and imports

Each .fea file is a module. A module may declare several geometries, meshes, materials, models, studies, sweeps, and execution policies. There is no one-study-per-file rule and no file-wide include.

Declarations and names

A top-level declaration has a kind, a name, and a body:

material aluminum_6061 {
    mass_density = 2700 kg/m^3
    elastic {
        youngs_modulus = 68.9 GPa
        poisson_ratio = 0.33
    }
}

Namespaces are explicit in references. material.aluminum_6061 cannot be confused with a model or geometry that happens to use the same local name. Nested declarations use their owning namespace, such as geometry.bracket.region.mounting_face or model.bracket.constraint.fixed_support.

Names are identities, not display labels. Rename a declaration through the language server so its references change with it.

Import one symbol

An import states the expected declaration kind, the local name, and the source file:

import geometry bracket from "./geometry/bracket.fea"
import mesh bracket from "./geometry/bracket.fea"
import material aluminum from "./materials/aluminum.fea"
import model mounting from "./models/mounting.fea"

Importing material aluminum does not import the other declarations in the file. Imports precede local declarations. Wildcard imports do not exist.

Paths are resolved relative to the importing file and must remain inside the admitted project or dependency source graph. RunMat rejects missing symbols, a symbol of the wrong kind, import cycles, paths outside the project, and changed source bytes after the project revision has been frozen.

Import a RunMat function

Use the same form for a named function defined by one .m file:

import function impactPulse from "./impactPulse.m"

The file must provide the named function entrypoint with a compatible typed signature. A script, an ambiguous definition, unapproved effects, or a changed source digest fails before numerical execution. See RunMat function integration for generated signals and geometry.

Composition is explicit

A model may include another model:

import model mounting from "./mounting.fea"

model bracket {
    include model.mounting
}

Inputs on the included model are bound by name. Composition retains the defining module for every object and rejects cycles, duplicate physical ownership, and conflicting assignments. Source order does not define precedence.

Source identity

The compiler records each logical module path, source digest, declaration span, imported symbol, and resolved dependency. Workers receive the resulting typed contracts and content-addressed artifacts; they do not receive source text and do not resolve imports again.

On this page
  • Declarations and names
  • Import one symbol
  • Import a RunMat function
  • Composition is explicit
  • Source identity