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.

/
See all docs
Builtin Reference
    • meshing.boundaryFaces
    • meshing.elements
    • meshing.evidence
    • meshing.generate
    • meshing.load
    • meshing.nodes
    • meshing.quality
    • meshing.regions
    • meshing.save

meshing.regions — List the persistent physical regions of a solver mesh.

regions = meshing.regions(mesh) returns a 1-by-R cell array with one struct per physical volume region of a meshing.Mesh.

Syntax

regions = meshing.regions(mesh)

Inputs

mesh
Type
Any
Required
Yes
Default
—
Description
meshing.Mesh from meshing.generate or meshing.load.
NameTypeRequiredDefaultDescription
meshAnyYes—meshing.Mesh from meshing.generate or meshing.load.

Returns

regions
Type
Any
Description
1-by-R cell of structs with id, kind, assembly_path, and element_count.
NameTypeDescription
regionsAny1-by-R cell of structs with id, kind, assembly_path, and element_count.

Errors

RunMat:meshing:InvalidInput
When
A meshing object, path, option, artifact, or evidence contract is invalid, or meshing cannot produce a result that satisfies the request.
Message
meshing operation failed
IdentifierWhenMessage
RunMat:meshing:InvalidInputA meshing object, path, option, artifact, or evidence contract is invalid, or meshing cannot produce a result that satisfies the request.meshing operation failed

Behavior

Each struct has id, the persistent region identifier that also appears in meshing.elements(mesh).region_ids; kind, the persistent entity kind (normally "region"); assembly_path, a cell column naming the assembly occurrence path in the source CAD; and element_count, the exact uint64 number of elements in the region.

Every retained tetrahedron belongs to exactly one region, so the element counts sum to the mesh's element_count. A single solid has one region; an assembly has one per solid occurrence.

Use in a study

Region identifiers select what mesh(solverMesh, 'Regions', id) displays. They are mesh identities, not material names: materials are assigned to geometry regions in the model, and those assignments are projected onto these mesh regions.

Errors

Every failure reports RunMat:meshing:InvalidInput, with a message that names the operation and the specific cause.

The input must be a meshing.Mesh.

Example

List the physical regions and their element counts

part = geometry.load('box.brep', 'Units', 'm');
solverMesh = meshing.generate(part, 'TargetSize', 0.5, 'MaximumDeviation', 0.05, 'ElementOrder', 'tet4', 'Seed', 42);
regions = meshing.regions(solverMesh);
body = regions{1};
body.element_count

Using meshing.regions with coding agents

Open a RunMat example with live inputs, then ask the agent to explain how meshing.regions changes the result.

Run a small meshing.regions example, explain the result, then change one input and compare the output.

FAQ

Why is the region id a long hash rather than a name?⌄

The identifier is derived from the exact CAD topology so that it stays stable across regeneration. Names come from the geometry and are applied by the model.

Related Meshing functions

meshing.boundaryFaces · meshing.elements · meshing.evidence · meshing.generate · meshing.load · meshing.nodes · meshing.quality · meshing.save

Related guides

  • Meshing
  • Mesh refinement guide

Source you can read

Every RunMat function's source is public. Read exactly how meshing.regions is executed, line by line, in Rust.

  • View the source for meshing.regions in Rust on GitHub
  • Learn how the RunMat runtime works
  • Found a bug? Open an issue with a minimal reproduction.

About RunMat

RunMat is a runtime that executes MATLAB-syntax code fast on any GPU. The runtime is free for individuals, including freelancers; students and faculty at an academic institution, for teaching or research there; contributors to an open-source project, for work on that project; organizations with 250 or fewer people and US$10M or less in annual revenue; and anyone, for non-production use. See runmat.com/license.

  • RunMat automatically optimizes your math for GPU execution on Apple, Nvidia, and AMD hardware. No code changes needed. Simulations that took hours now take minutes.
  • Start running code in seconds. RunMat runs in the browser, on the desktop, or from the CLI. No license server, no IT ticket.

Getting started · Benchmarks · Pricing

Download RunMat

Download RunMat for full performance, or use RunMat in your browser for zero setup.

Download RunMatOpen Sandbox
On this page
  • Syntax
  • Inputs
  • Returns
  • Errors
  • Behavior
  • Use in a study
  • Errors
  • Example
  • List the physical regions and their element counts
  • Using meshing.regions with coding agents
  • FAQ
  • Related Meshing functions
  • Related guides
  • Source you can read
  • About RunMat