geometry.facesIntroducedBy — Select the faces a geometry operation created, using topology history.
output = geometry.facesIntroducedBy(feature) returns a face geometry.RegionOutput that selects the faces introduced by feature's own operation and requires at least one.
Syntax
output = geometry.facesIntroducedBy(feature)Inputs
feature- Type
Any- Required
- Yes
- Default
- —
- Description
- geometry.Feature whose introduced faces are selected.
Returns
output- Type
Any- Description
- Face geometry.RegionOutput selected by the feature's topology history.
Errors
RunMat:geometry:facesIntroducedBy:InvalidInput- When
- The wrong number of arguments is passed. The argument is not a geometry.Feature. A value violates the feature-graph contract.
- Message
geometry.facesIntroducedBy: invalid input
Behavior
Introduced faces are those the CAD kernel reports as generated by the operation, together with result faces that have no predecessor in its inputs: the wall and floor of a hole, the bore surface of a subtraction, the blend faces of a fillet, or the side faces of an extrusion. Faces inherited from the inputs are excluded.
Resolution requires complete topology history for the operation; if the kernel cannot prove complete lineage, realization fails instead of guessing from geometric proximity. Selections are defined by feature lineage, not by entity index or position. Because the region names what the feature produced, it keeps selecting the intended topology when dimensions change and the part is regenerated, and realization fails rather than silently selecting different topology.
Creating the selection is a pure, non-suspending call; it does not realize geometry.
Use in a study
This is the usual way to name load and support surfaces on generated geometry: publish geometry.facesIntroducedBy(holed) as a bore region and apply a bearing load or fixed support to it in .fea.
Errors
RunMat:geometry:facesIntroducedBy:InvalidInput reports a call that does not pass exactly one geometry.Feature value. Selection errors at realization, such as an empty selection, a cardinality mismatch, or missing topology history, are reported by the .fea geometry materialization that resolves the region, before meshing or assembly.
Example
Name the wall of a drilled hole
plate = geometry.box(80e-3, 50e-3, 8e-3);
holed = geometry.hole(plate, 4e-3, 8e-3, [0 0 1], [40e-3 25e-3 0]);
part = geometry.finish(holed);
part = geometry.withRegion(part, "bore", geometry.facesIntroducedBy(holed));
class(part)Using geometry.facesIntroducedBy with coding agents
Open a RunMat example with live inputs, then ask the agent to explain how geometry.facesIntroducedBy changes the result.
Run a small geometry.facesIntroducedBy example, explain the result, then change one input and compare the output.
FAQ
Does a primitive introduce faces?⌄
Yes. A primitive has no inputs, so all of its faces are introduced by it.
Related Geometry functions
Construction
geometry.box · geometry.chamfer · geometry.cylinder · geometry.edges · geometry.edgesIntroducedBy · geometry.extrude · geometry.faces · geometry.fillet · geometry.finish · geometry.hole · geometry.instance · geometry.intersect · geometry.pocket · geometry.revolve · geometry.solid · geometry.sphere · geometry.subtract · geometry.transform · geometry.union · geometry.withRegion
Related guides
Source you can read
Every RunMat function's source is public. Read exactly how geometry.facesIntroducedBy is executed, line by line, in Rust.
- View the source for geometry.facesIntroducedBy 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.