fea.model — Assemble a typed RunMat FEA model.
fea.model(id, geometry, Name, Value, ...) assembles an analysis model from a geometry.Asset and typed RunMat FEA components.
Syntax
model = fea.model(id, geometry, Name, Value, ...)Inputs
| Name | Type | Required | Default | Description |
|---|---|---|---|---|
id | StringScalar | Yes | — | Model id. |
geometry | Any | Yes | — | Existing geometry.Asset object. |
Name, Value | Any | Variadic | — | Profile, frame, defaults, and typed model-component options. |
Returns
| Name | Type | Description |
|---|---|---|
result | Any | FEA object or operation result. |
Errors
| Identifier | When | Message |
|---|---|---|
RunMat:fea:LoadFailed | A .fea document cannot be read, parsed, or resolved. | fea: failed to load FEA document |
RunMat:fea:InvalidInput | A builtin receives an unsupported argument pattern or object type. | fea: invalid input |
RunMat:fea:OperationFailed | A validation, planning, run, result-query, comparison, or trend operation fails. | fea: operation failed |
RunMat:fea:Internal | An FEA object or operation result cannot be converted to a RunMat value. | fea: internal error |
How fea.model works
- Model id and component identities remain exact structural values; the geometry revision is copied exactly into the model.
- Profile, frame, defaults mode, materials, assignments, boundaries, loads, steps, domains, and interfaces are validated during assembly.
- Numeric physics values must already have crossed their owning constructor's explicit binary64 boundary;
fea.modeldoes not reinterpret integer arrays as components. - Model assembly consumes an existing geometry asset and does not intrinsically require native OCCT. OCCT is only relevant when a topology-bearing CAD file must first be imported.
Example
Assemble an explicit model
model = fea.model("bracket", geom, "Materials", {steel}, "Loads", {tipLoad});Using fea.model with coding agents
Open a RunMat example with live inputs, then ask the agent to explain how fea.model changes the result.
Run a small fea.model example, explain the result, then change one input and compare the output.
FAQ
Does fea.model import CAD?⌄
No. Pass a geometry.Asset. CAD import is a separate geometry operation and only some CAD formats require an OCCT-enabled importer.
Related Fea functions
fea.boundaryCondition · fea.compare · fea.domain · fea.field · fea.interface · fea.loadCase · fea.material · fea.materialAssignment · fea.plan · fea.plot · fea.results · fea.run · fea.runOptions · fea.step · fea.study · fea.sweep · fea.trends · fea.validate
Open-source implementation
Unlike proprietary runtimes, every RunMat function is open-source. Read exactly how fea.model is executed, line by line, in Rust.
- View the source for fea.model in Rust on GitHub
- Learn how the RunMat runtime works
- Found a bug? Open an issue with a minimal reproduction.
About RunMat
RunMat is an open-source runtime that executes MATLAB-syntax code blazing on any GPU. It is licensed under the Apache 2.0 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.