meshing.boundaryFaces — Return solver-mesh boundary triangles with roles, adjacency, and CAD provenance.
faces = meshing.boundaryFaces(mesh) returns a struct describing every boundary face of a meshing.Mesh: identifiers, node connectivity, boundary role, adjacent elements, and the exact CAD entities each face came from.
Syntax
faces = meshing.boundaryFaces(mesh)Inputs
mesh- Type
Any- Required
- Yes
- Default
- —
- Description
- meshing.Mesh from meshing.generate or meshing.load.
Returns
faces- Type
Any- Description
- Struct with ids, connectivity, roles, adjacent_element_ids, and provenance.
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
Behavior
ids is an F-by-1 uint64 column. connectivity is F-by-3 for Tri3 faces of Tet4 meshes and F-by-6 for Tri6 faces of Tet10 meshes, holding node identifiers from meshing.nodes. roles is an F-by-1 cell with "exterior", "conformal_interface", "contact_primary", or "contact_secondary".
adjacent_element_ids is an F-by-1 cell whose entries are 1-by-n uint64 rows of the volume elements that share the face: one for an exterior face, two for an interface between regions. provenance is an F-by-1 cell whose entries are 1-by-p cells of structs with kind (for example "face"), source_topology_id, and assembly_path, naming the persistent CAD entities the face lies on.
Rows are aligned across all fields. The call decodes the mesh in memory and does not touch the filesystem.
Use in a study
Provenance is what connects solver faces back to CAD faces: boundary conditions applied to a geometry region are projected onto exactly the mesh faces whose provenance names that region's faces. Use it to audit which triangles a load or support will act on.
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; a mesh that mixes boundary connectivity widths is rejected.
Example
Count exterior faces and read their CAD provenance
part = geometry.load('box.brep', 'Units', 'm');
solverMesh = meshing.generate(part, 'TargetSize', 0.5, 'MaximumDeviation', 0.05, 'ElementOrder', 'tet4', 'Seed', 42);
faces = meshing.boundaryFaces(solverMesh);
exterior = sum(strcmp(faces.roles, 'exterior'))
firstOwner = faces.provenance{1}{1}Using meshing.boundaryFaces with coding agents
Open a RunMat example with live inputs, then ask the agent to explain how meshing.boundaryFaces changes the result.
Run a small meshing.boundaryFaces example, explain the result, then change one input and compare the output.
FAQ
Why do some faces have two adjacent elements?⌄
Interior faces between two regions, such as bonded parts of an assembly, are reported as conformal_interface faces shared by one element on each side.
Related Meshing functions
meshing.elements · meshing.evidence · meshing.generate · meshing.load · meshing.nodes · meshing.quality · meshing.regions · meshing.save
Related guides
Source you can read
Every RunMat function's source is public. Read exactly how meshing.boundaryFaces is executed, line by line, in Rust.
- View the source for meshing.boundaryFaces 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.