geometry.edges — Select the edges produced by a geometry feature.
output = geometry.edges(feature) returns an edge geometry.RegionOutput that selects the edges of feature's result and requires at least one.
Syntax
output = geometry.edges(feature)Inputs
feature- Type
Any- Required
- Yes
- Default
- —
- Description
- geometry.Feature whose result edges are selected.
Returns
output- Type
Any- Description
- Edge geometry.RegionOutput that must resolve to one or more edges.
Errors
RunMat:geometry:edges: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.edges: invalid input
Behavior
The selection resolves, when realized, to the edges of feature's own result that are present in the part being built. It is the edge input to geometry.fillet and geometry.chamfer, and it can also be published as an edge region.
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
Pass the selection to geometry.fillet or geometry.chamfer, or publish it with geometry.withRegion for an edge region in .fea.
Errors
RunMat:geometry:edges: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
Select every edge of a block for a chamfer
block = geometry.box(40e-3, 40e-3, 20e-3);
allEdges = geometry.edges(block);
beveled = geometry.chamfer(block, allEdges, 1e-3);
class(allEdges)Using geometry.edges with coding agents
Open a RunMat example with live inputs, then ask the agent to explain how geometry.edges changes the result.
Run a small geometry.edges example, explain the result, then change one input and compare the output.
FAQ
Why does fillet reject my selection?⌄
geometry.fillet and geometry.chamfer require edge selections. geometry.faces and geometry.solid select other topology.
Related Geometry functions
Construction
geometry.box · geometry.chamfer · geometry.cylinder · geometry.edgesIntroducedBy · geometry.extrude · geometry.faces · geometry.facesIntroducedBy · 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.edges is executed, line by line, in Rust.
- View the source for geometry.edges 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.