fea.step — Create a typed FEA analysis step.
fea.step(id, kind) creates a fea.Step from a text identifier and analysis kind.
Syntax
step = fea.step(id, kind)Inputs
| Name | Type | Required | Default | Description |
|---|---|---|---|---|
id | StringScalar | Yes | — | Analysis-step id. |
kind | StringScalar | Yes | — | Static, modal, transient, thermal, nonlinear, electromagnetic, or CFD step kind. |
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.step works
- Exactly two text scalar inputs are required. Supported kinds are the analysis step kinds exposed by the selected model family.
- Direct integer and resident numeric inputs have no role and reject before object construction.
- The constructor is host-side and does not invoke a solver, provider, or native OCCT geometry path.
Example
Create a transient step
step = fea.step("transient_1", "transient");Using fea.step with coding agents
Open a RunMat example with live inputs, then ask the agent to explain how fea.step changes the result.
Run a small fea.step example, explain the result, then change one input and compare the output.
FAQ
Where are step counts configured?⌄
Use the solver-specific fea.runOptions count fields; fea.step only identifies a typed analysis step.
Related Fea functions
fea.boundaryCondition · fea.compare · fea.domain · fea.field · fea.interface · fea.loadCase · fea.material · fea.materialAssignment · fea.model · fea.plan · fea.plot · fea.results · fea.run · fea.runOptions · fea.study · fea.sweep · fea.trends · fea.validate
Open-source implementation
Unlike proprietary runtimes, every RunMat function is open-source. Read exactly how fea.step is executed, line by line, in Rust.
- View the source for fea.step 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.