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.

/
    • The design language
    • Values, units and expressions
    • Names and selectors
    • Folders, modules and use
    • MATLAB functions in design values
    • Checks and diagnostics
    • Agent tools and the command line
    • Feature status
    • Design commands
Docs>CAD

Checks and diagnostics

The editor checks a design file on every change, and the agent and the command line run the same check. A check regenerates the design: a part rebuilds its feature history, an assembly resolves its occurrences and solves its mates, a drawing compiles against the models its views show, and a circuit elaborates and runs its electrical rules. The result lists every problem with where it is written and what it affects.

What a diagnostic holds

FieldMeaning
severityerror, warning or info. An error stops the design from regenerating cleanly.
codeA stable code, such as cad.ref.not_generated or cad.asm.mate_conflict.
messageWhat is wrong, naming the item: body ran but no longer makes body.side(l9).
causeroot (fix this one) or cascade (failed because of a root).
rootFor a cascade: the root diagnostic it follows from.
subjectThe item it is about, by canonical ID: feature.round, mate.hinge, occurrence.wing/rib@ribs[2], U3.
failed_featuresFor a root: the features that failed or were blocked because of it.
rangeWhere it is written in the file.
repairsTyped fixes the compiler offers; the editor applies one with a click, and the agent can apply it too.

A broken reference fails its own feature and blocks the features after it that use what it made. The check reports one root and lists the blocked features under it, so a single broken fillet never reads as a dozen errors.

Example: a reference that no longer resolves

The fillet below names the side face of a sketch line l9 that the sketch does not have. The check fails at the fillet, and the rest of the part still regenerates.

runmat 0.7
std 1

part bracket {
    sketch s1 on origin.xy {
        l1 = line(start = [0 mm, 0 mm], end = [80 mm, 0 mm])
        l2 = line(start = [80 mm, 0 mm], end = [80 mm, 50 mm])
        l3 = line(start = [80 mm, 50 mm], end = [0 mm, 50 mm])
        l4 = line(start = [0 mm, 50 mm], end = [0 mm, 0 mm])
    }
    feature body = extrude(profile = sketch.s1, distance = 10 mm)
    feature round = fillet(
        edges = [edges_between(feature.body.face.side(s1.l9), feature.body.face.end)],
        radius = 1 mm
    )
    output bracket = { body = feature.body.body, part_number = "BR-100" }
}

The check reports body ran but no longer makes body.side(l9) as a root cause on feature.round, with the range of the reference.

Code families

PrefixCovers
cad.ref.*References: an entity the maker no longer makes (not_generated), a reference to a later feature (forward_reference), ambiguous or empty selections, kind mismatches
cad.xref.*Reads from other files: an unknown file, a name it does not publish, a missing pinned revision
cad.sketch.*Sketches: over- or under-constrained, redundant constraints, open profiles
cad.regen.*, cad.kernel.*Regeneration: cascades, operations the geometry kernel could not build
cad.region.expectationA region that found more or fewer entities than its expect
cad.asm.*Assemblies: unknown designs and occurrences, cycles, mates that conflict, are redundant or leave parts under-defined, configuration problems, interference and clearance
cad.fastener.*Fastener sets: paths, exceptions, fits and tables
cad.pmi.*, cad.drawing.*PMI references and semantics, drawing references, hole tables
cad.property.*Missing or invalid properties
design.value.*Values from .m functions: unit mismatches, nondeterminism, failures

A circuit check reports ERC findings (unconnected pins, outputs driven together, missing power flags), and a board check adds DRC findings, unrouted connections and schematic changes the board has not taken yet. See Rules and checks.

Checking from the command line

runmat-design check checks circuits and boards, prints each finding, and exits with status 1 when any file has an error, so a CI job or a coding agent can gate on it:

runmat-design check board/flight_controller.circuit.layout
runmat-design check board/*.circuit --json
OptionEffect
--jsonPrint the reports as JSON.
--no-simulateSkip the simulation sections' measures.
--interferenceOn an assembly, also check for overlapping parts.
--root <dir>The workspace root, when it is not the file's folder.

runmat check <file>.circuit and runmat test run the same circuit checks beside .m and .fea files, with the same --no-simulate option.

runmat-design check also checks .part, .assembly and .drawing files with the editor's check: it regenerates the part, resolves the assembly's occurrences, mates and patterns, or compiles the drawing's views, prints each diagnostic with its line, and exits with status 1 on any error. --interference also checks an assembly for parts that share material, the Evaluate tab's interference check, and fails on any overlap; parts that only touch don't count. Every body of a multi-body part is checked, and each overlap names the first pair of bodies found. Bodies of compressible fill (batt and loose-fill insulation) are left out and counted, because a cable, pipe or box in an insulated cavity displaces the fill:

runmat-design check house/house.assembly --interference --root house

runmat check and runmat test take those files too Not yet releasedStatus.

On this page
  • What a diagnostic holds
  • Example: a reference that no longer resolves
  • Code families
  • Checking from the command line