geometry.box — Create an exact rectangular box feature from SI dimensions.
feature = geometry.box(width, depth, height) returns a geometry.Feature for an axis-aligned rectangular solid with one corner at the origin and extents width along +x, depth along +y, and height along +z, in meters.
Syntax
feature = geometry.box(width, depth, height)Inputs
width- Type
NumericScalar- Required
- Yes
- Default
- —
- Description
- Positive extent along +x, in meters.
depth- Type
NumericScalar- Required
- Yes
- Default
- —
- Description
- Positive extent along +y, in meters.
height- Type
NumericScalar- Required
- Yes
- Default
- —
- Description
- Positive extent along +z, in meters.
Returns
feature- Type
Any- Description
- geometry.Feature for an axis-aligned box with one corner at the origin.
Errors
RunMat:geometry:box:InvalidInput- When
- The wrong number of arguments is passed. A dimension is not a real numeric scalar. A value violates the feature-graph contract.
- Message
geometry.box: invalid input
Behavior
The box occupies [0, width] x [0, depth] x [0, height]. Place it elsewhere with geometry.transform, combine it with geometry.union, geometry.subtract, or geometry.intersect, or cut it with geometry.hole and geometry.pocket.
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.
A box is the usual stock for plates, brackets, and blocks. Cut features from it, then publish geometry.solid(body) as the material region and geometry.facesIntroducedBy selections as boundary regions.
Errors
RunMat:geometry:box:InvalidInput reports every failure of the call: the wrong number of arguments, a dimension that is not a real numeric scalar, 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
Create mounting-plate stock
% 80 mm x 50 mm x 8 mm plate, entered in meters
plate = geometry.box(80e-3, 50e-3, 8e-3);
class(plate)A zero dimension is rejected
plate = geometry.box(80e-3, 50e-3, 0);Using geometry.box with coding agents
Open a RunMat example with live inputs, then ask the agent to explain how geometry.box changes the result.
Run a small geometry.box example, explain the result, then change one input and compare the output.
FAQ
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.
Where is the box placed?⌄
One corner is at the origin and the box extends along +x, +y, and +z. Use geometry.transform with a 4-by-4 homogeneous matrix to move or rotate it.
Can I display or mesh a feature directly in a script?⌄
Not yet. geometry.Feature and geometry.Generated are construction values; mesh and meshing.generate accept a loaded geometry.Asset. Realization happens when a .fea geometry declaration imports the generating function.
Related Geometry functions
Construction
geometry.chamfer · geometry.cylinder · geometry.edges · 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.box is executed, line by line, in Rust.
- View the source for geometry.box 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.