geometry.extrude — Sweep a face profile along a straight direction to make a prism.
feature = geometry.extrude(profile, distance, direction) returns a geometry.Feature for the linear sweep of profile by distance meters along direction.
Syntax
feature = geometry.extrude(profile, distance, direction)Inputs
profile- Type
Any- Required
- Yes
- Default
- —
- Description
- geometry.Feature whose result is a face or sheet.
distance- Type
NumericScalar- Required
- Yes
- Default
- —
- Description
- Positive sweep length in meters.
direction- Type
NumericArray- Required
- Yes
- Default
- —
- Description
- Finite nonzero three-element sweep direction.
Returns
feature- Type
Any- Description
- geometry.Feature for the linear sweep of profile.
Errors
RunMat:geometry:extrude:InvalidInput- When
- The wrong number of arguments is passed. profile is not a geometry.Feature, distance is not a real numeric scalar, or direction is not a finite three-element real vector. A value violates the feature-graph contract.
- Message
geometry.extrude: invalid input
Behavior
distance is a positive length in meters and direction is a nonzero three-element direction; only its direction is used. The sweep is one-sided, starting at the profile.
The profile must realize as a face or sheet; sweeping a face produces a solid. A solid cannot be swept, so a profile built from geometry.box, geometry.cylinder, or geometry.sphere is accepted at construction but rejected when the graph is realized. The programmatic builder does not yet provide sketch or planar-face constructors.
The call records construction intent only. It appends one operation to an immutable, content-addressed feature graph and returns a new geometry.Feature; it does not run a CAD kernel, tessellate, or touch the filesystem. The graph is realized as exact B-rep topology when a .fea geometry declaration that imports the generating function is materialized for meshing or analysis.
All lengths are meters and all angles are radians; there is no unit option. Scalars accept double, single, or an exactly representable integer-class scalar. Vector arguments must be real, finite, non-integer-class numeric arrays with the stated element count; row and column orientation are both accepted.
Every failure, including the wrong number of arguments, a value of the wrong kind, and a value that violates the feature-graph contract (a nonpositive or non-finite length, radius, depth, distance, or angle, or an all-zero direction), raises the builtin's own RunMat:geometry:<name>:InvalidInput identifier, and no value is returned. Feature identities are derived from a digest of each operation, so repeating the same construction yields the same feature identity.
Use in a study
Return the finished part from a pure .m function: geometry.finish(feature) turns the final feature into a geometry.Generated product, and geometry.withRegion publishes typed selections under names. A .fea geometry declaration written as generated by function.<name> calls that function, realizes the exact geometry, and exposes each named selection as output.region.<name> for meshing, material assignment, constraints, and loads.
geometry.facesIntroducedBy(extrusion) selects the side and cap faces created by the sweep.
Errors
RunMat:geometry:extrude:InvalidInput reports every failure of the call: the wrong number of arguments, a profile that is not a geometry.Feature, a distance that cannot be converted, or a direction that is not a finite three-element real vector, or a value that violates the feature-graph contract, such as a zero or negative dimension, a non-finite value, or an all-zero direction. A failed call returns nothing, and earlier values are unchanged because builder values are immutable.
Examples
Record a 50 mm extrusion along z
profile = geometry.box(20e-3, 10e-3, 1e-3);
bar = geometry.extrude(profile, 50e-3, [0 0 1]);
class(bar)An all-zero direction is rejected
profile = geometry.box(20e-3, 10e-3, 1e-3);
bar = geometry.extrude(profile, 50e-3, [0 0 0]);Using geometry.extrude with coding agents
Open a RunMat example with live inputs, then ask the agent to explain how geometry.extrude changes the result.
Run a small geometry.extrude example, explain the result, then change one input and compare the output.
FAQ
Why does my extrusion of a box fail when the study runs?⌄
A box is a solid, and only faces or sheets can be swept. Construction records the operation; realization rejects the solid profile.
How do I enter millimeter dimensions?⌄
Convert to meters before the call, for example geometry.box(80e-3, 50e-3, 8e-3). When the function is called from a .fea declaration, length inputs already arrive in meters.
Related Geometry functions
Construction
geometry.box · geometry.chamfer · geometry.cylinder · geometry.edges · geometry.edgesIntroducedBy · 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.extrude is executed, line by line, in Rust.
- View the source for geometry.extrude 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.