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

Names and selectors

A reference names what it points at by how the design made it, never by a number the kernel happened to assign. feature.body.face.end is the face the body extrude made at the end of its extent; feature.body.face.side(outline.l1) is the side face the sketch line l1 swept. When the sketch gains a line or an earlier feature changes, these names still point at the same faces, and a reference that can no longer resolve is an error at the reference, with the features that depend on it.

Kinds and heads

Every reference starts with the kind of item it names:

HeadNamesExample
inputan inputinput.width
leta let valuelet.half
sketcha sketch, its loops or one of its pointssketch.outline, sketch.outline.l1.end
featurea feature, and the bodies, faces, edges and vertices it madefeature.body.face.end
originthe part's origin planes, axes and pointorigin.xy, origin.z, origin.point
plane, axis, pointa datum feature of that kindplane.mid, axis.hinge
regiona named selectionregion.top
materiala materialmaterial.aluminum
part, assemblyanother designpart.bracket.mass
net, port, bus, instancecircuit connectionsnet.GND, port.IN, bus.D.D0

The kind keyword keeps a reference's meaning fixed: a material steel and a feature steel can share a name, and adding a file to the folder never changes what an existing reference means.

Faces, edges and bodies

feature.<name>.<topology>.<role> names an entity by the feature that made it and the role it plays:

FormSelects
feature.body.bodythe solid body the feature made
feature.body.face.start, feature.body.face.endthe faces at the start and end of an extrude, revolve or sweep
feature.body.face.side(outline.l1)the face the sketch curve outline.l1 swept
feature.body.face.side(outline.l1, ordinal = 2)one piece of a side face that a later feature split
feature.bolt.face.wall(a)the wall of the hole at the key a
feature.halve.face.split_face(side = positive)the face a split made, on one side
feature.base.face.sheet(base, ordinal = 0)a sheet-metal face from the sketch line base
feature.step.face("Top")a face named in an imported CAD file

The roles a feature gives its faces: side, start, end, blend (fillet), chamfer, wall, bottom, counterbore, counterbore_wall, countersink (holes), inner, outer, rim (shell), thin_wall, draft_step, split_face, boundary, patch, offset, extension, thicken, thicken_rim, mid_surface, ruled (surfaces), sheet, sheet_edge, bend, relief, form (sheet metal), member_side, member_end, cap_plate, gusset, weld_bead (weldments), parting (mold), thread, emboss_top and rib.

Relational selectors

Where an entity has no single maker, name it by the entities around it:

FormSelects
edges_between(a, b)the edges where faces a and b meet
vertex_of(a, b, c)the vertex where three faces meet
piece(a, bounded_by = [b])the piece of face a bounded by b
point(10 mm, 0 mm, 5 mm)a point in part coordinates

This part rounds the edge between its first side face and its top face, drills a hole on its top face, and names the top face as a region:

runmat 0.7
std 1

part block {
    sketch outline on origin.xy {
        l1 = line(start = [0 mm, 0 mm], end = [60 mm, 0 mm])
        l2 = line(start = [60 mm, 0 mm], end = [60 mm, 40 mm])
        l3 = line(start = [60 mm, 40 mm], end = [0 mm, 40 mm])
        l4 = line(start = [0 mm, 40 mm], end = [0 mm, 0 mm])
    }
    feature body = extrude(profile = sketch.outline, distance = 20 mm)
    feature bolt = hole(
        face = feature.body.face.end,
        at = { a = point(30 mm, 20 mm, 20 mm) },
        diameter = 6.6 mm,
        through_all
    )
    feature round = fillet(
        edges = [edges_between(feature.body.face.side(outline.l1), feature.body.face.end)],
        radius = 2 mm
    )

    region top : face = { select = [feature.body.face.end], expect = exactly_one }
    region bore : face = { select = [feature.bolt.face.wall(a)], expect = at_least_one, label = "Bolt bore" }

    publish top = region(region = top)

    output block = { body = feature.body.body, part_number = "BK-60" }
}

Regions

A region is a named, checked selection. region <name> : <kind> = { select = […], expect = … } selects faces, edges, vertices or bodies, and expect states how many it must find:

expectMeaning
exactly_oneone entity; zero or several is an error
at_least_oneone or more
anyzero is allowed

label gives the region the name its faces carry in a STEP export, so a study selects them with select name "Bolt bore". body = feature.<name>.body limits a region to one body's copy of a shared face, as when a fluid body fills a part.

Published names

publish makes an item readable from other files under a stable name. An assembly attaches to a published frame, a drawing dimensions a published face, and another part reads a published value:

FormPublishes
publish top = region(region = top)a region
publish pitch = value(input = pitch)an input's value
publish half = let(name = half)a let's value

Another file reads a published value as part.<design>.publish.<name>. See Outputs, regions and published values.

Occurrences in an assembly

An assembly names each placed part or sub-assembly by its occurrence name. Paths go down through sub-assemblies with /, and copies made by a pattern or a mirror carry the pattern and the copy's key:

FormNames
wing_leftthe occurrence wing_left
wing/ribrib inside the sub-assembly occurrence wing
rib@ribs[3]the copy of rib at key 3 of the pattern ribs
rivet0@rivets_port[3]the mirror rivets_port's image of the copy at key 3

Pins, nets and designators

A circuit names connections by component and pin:

FormNames
U1.VINpin VIN of U1
U.A.OUTpin OUT of unit A of U
"C1.1"pin 1 of C1 (quoted, since 1 is not a word)
net.GND, "net.+3V3"a net
port.INa sheet port
bus.D.D0a bus member
instance.pwr.VINa port of a sheet instance
"instance.ch.VIN#2"that port on one channel of a repeated instance

A net inside a repeated sheet takes its instance path: the FBK net of the first copy of ch is /ch[0]/FBK on the board.

Canonical IDs

The editor, the agent and the 3D view select items by one canonical ID each, such as feature.boss, mate.m1, occurrence.wing/rib@ribs[2], net:GND or component:U3. A selection made in one view is the same selection in every other: picking U3 on the schematic lights its pads on the board and its body in 3D. Diagnostics name their subject with the same IDs.

On this page
  • Kinds and heads
  • Faces, edges and bodies
  • Relational selectors
  • Regions
  • Published names
  • Occurrences in an assembly
  • Pins, nets and designators
  • Canonical IDs