fea.sweep — Create a deterministic FEA study sweep.
fea.sweep(id, studies, Name, Value, ...) creates a fea.Sweep from one study or a cell array of studies.
Syntax
sweep = fea.sweep(id, studies, Name, Value, ...)Inputs
| Name | Type | Required | Default | Description |
|---|---|---|---|---|
id | StringScalar | Yes | — | Sweep id. |
studies | Any | Yes | — | A fea.Study or cell array of fea.Study objects. |
Name, Value | Any | Variadic | — | Optional logical FailFast control. |
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.sweep works
- The required inputs are a text sweep id and one
fea.Studyor cell array offea.Studyobjects. FailFastis the only option. It defaults to true and accepts a logical scalar; numeric and resident controls reject before construction.- The direct integer audit is not applicable because integers have no study/id role and
FailFastis logical-only. - Public study counts and indexes remain exact typed integers. The constructor is host-side and does not execute providers or intrinsically require native OCCT.
Example
Continue after failed studies
sweep = fea.sweep("variants", {studyA, studyB}, "FailFast", false);Using fea.sweep with coding agents
Open a RunMat example with live inputs, then ask the agent to explain how fea.sweep changes the result.
Run a small fea.sweep example, explain the result, then change one input and compare the output.
FAQ
Does creating a sweep run its studies?⌄
No. fea.sweep creates the typed definition; pass it to fea.validate, fea.plan, or fea.run.
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.step · fea.study · fea.trends · fea.validate
Open-source implementation
Unlike proprietary runtimes, every RunMat function is open-source. Read exactly how fea.sweep is executed, line by line, in Rust.
- View the source for fea.sweep 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.