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.

/
    • Sketches and constraints
    • Features
    • Outputs, regions and published values
    • Configurations
    • Occurrences and mates
    • Patterns, mirrors and fasteners
    • Drawing views and annotations
    • Evaluate
    • Import and export
    • Scripting and sweeps
Docs>CAD>MCAD reference

Outputs, regions and published values

A part's feature history makes geometry. The statements on this page say what that geometry is to the rest of the project: which body is the part and what it is made of, which faces carry names, which values other files may read, and what the manufacturing tolerances are. This bracket uses each of them.

runmat 0.7
std 1

part bracket {
    input width : length = 80 mm
    input depth : length = 50 mm
    input thickness : length = 10 mm

    sketch s1 on origin.xy {
        l1 = line(start = [0 mm, 0 mm], end = [input.width, 0 mm])
        l2 = line(start = [input.width, 0 mm], end = [input.width, input.depth])
        l3 = line(start = [input.width, input.depth], end = [0 mm, input.depth])
        l4 = line(start = [0 mm, input.depth], end = [0 mm, 0 mm])
    }
    feature body = extrude(profile = sketch.s1, distance = input.thickness)
    feature mount = hole(face = feature.body.face.end, at = { a = point(15 mm, 25 mm, 10 mm), b = point(65 mm, 25 mm, 10 mm) }, diameter = 6.6 mm, through_all)
    feature round = fillet(edges = [edges_between(feature.body.face.side(s1.l1), feature.body.face.end)], radius = 1.5 mm)

    output bracket = { body = feature.body.body, part_number = "BR-100", material = "material.aluminum_6061" }

    region top : face = { select = [feature.body.face.end], expect = exactly_one }
    region mounting : face = { select = [feature.mount.face.wall(a), feature.mount.face.wall(b)], expect = at_least_one, label = "Mounting bores" }
    publish top = region(region = top)
    publish thickness = value(input = thickness)

    datum A = { on = feature.body.face.start }
    datum B = { on = feature.body.face.side(s1.l1) }
    tolerance top_flat = { characteristic = flatness, on = [feature.body.face.end], tolerance = 0.05 mm }
    tolerance top_parallel = { characteristic = parallelism, on = [feature.body.face.end], tolerance = 0.1 mm, datums = [{ label = A, modifier = rfs }] }
    size bore = { on = [feature.mount.face.wall(a)], size = 6.6 mm ± [0.1 mm, 0 mm] }
    location bore_to_edge = { from = feature.body.face.side(s1.l4), to = feature.mount.face.wall(a), distance = 15 mm ± 0.1 mm }
    finish seat = { on = [feature.body.face.start], ra = 1.6 um }

    configuration long = { width = 120 mm, part_number = "BR-120" }
    configuration plain = { suppress = [feature.round], part_number = "BR-100-P" }
    configuration thick = { features = { body = { distance = 12 mm } }, part_number = "BR-100-T" }

    link verifies feature.body to "checks/bracket_static.fea#check.max_stress"
}

Outputs

output <name> = { … } declares a part the file delivers: the body, and the identity the BOM, title blocks and STEP carry. A file may declare several outputs, such as a fluid body beside the solid it fills.

FieldMeaning
bodyThe body: feature.<name>.body.
part_numberThe part number. A configuration can set its own.
materialThe material, as "material.<name>". Mass properties read its density.
colorThe display color, "#RRGGBB" or "#RRGGBBAA", when it differs from the material's appearance.
labelThe product name in a STEP export, when it differs from the output's name. A study selects the body by it.
propertiesTyped properties, such as density = 1450 kg/m^3 for a body whose material the density table does not know.

material = { body = feature.<name>.body, material = "material.<name>" } sets the material of one body; bodies with no assignment take their output's material. Mass properties match the material name's words against a table of common alloys, plastics and composites (aluminum_6061, steel_300m, carbon_prepreg, nylon); a density property on the output overrides the table.

Regions

A region names a selection and checks its count. The selection forms and expect values are in Names and selectors. Regions travel with the geometry: a STEP export names the faces by the region's label (or its name), so a study writes select name "Mounting bores" and keeps working when the part changes.

Published values

publish makes an item readable from other files by a stable name:

FormPublishesRead elsewhere as
publish top = region(region = top)a regionan assembly's attachment, a drawing's references
publish thickness = value(input = thickness)an input's value, with its unitpart.bracket.publish.thickness
publish half = let(name = half)a let's valuepart.bracket.publish.half

A skeleton part publishes the frames and values a whole assembly is laid out from; parts and assemblies read them, and a change to the skeleton flows to every reader. Across project partitions a read is pinned to a released revision (use part skeleton from "//wing/skeleton" @ "R3" as sk).

PMI

PMI is part of the part, attached by the same references as features and regions. Drawings show it (a GD&T frame on a view names a tolerance here rather than restating it), and STEP AP242 exports carry it as semantic PMI.

StatementDeclaresFields
datum A = { on = … }a datum featureon: a face
tolerance <name> = { … }a geometric tolerancecharacteristic, on, tolerance, datums, diametral, modifier, projected
size <name> = { … }a toleranced size or a fiton, size (a toleranced value), fit (such as "H7")
location <name> = { … }a toleranced distance between two featuresfrom, to, distance
finish <name> = { … }a surface finishon, ra, process

Characteristics: straightness, flatness, circularity, cylindricity (form; no datums); profile_of_line, profile_of_surface; parallelism, perpendicularity, angularity (orientation); position, concentricity, symmetry (location); circular_runout, total_runout. Orientation, location and runout tolerances need at least one datum. A datum reference is { label = A, modifier = rfs }, with the material condition rfs, mmc or lmc.

The check resolves every attachment against the regenerated part and checks the semantics: datum labels unique and declared, form tolerances without datums, orientation and location tolerances with them, and tolerance values of the right dimension.

Links

link <kind> <item> to "<target>" records a traceable relation from an item in this file to another file:

KindMeaning
verifiesA study or check verifies the item: link verifies feature.body to "checks/bracket_static.fea#check.max_stress".
derived_fromThe item was derived from the target, such as a supplier model.
supersedesThe item replaces the target.
supplier_docThe target is the supplier's document for the item.

The item is a feature (feature.body), a region, a published name or an output.

On this page
  • Outputs
  • Regions
  • Published values
  • PMI
  • Links