fea.validate — Validate a RunMat FEA study or sweep without solving.
fea.validate(studyOrSweepOrPath) validates one typed study, a sweep, or a .fea document and writes validation evidence.
Syntax
result = fea.validate(studyOrSweepOrPath)Inputs
| Name | Type | Required | Default | Description |
|---|---|---|---|---|
study | Any | Yes | — | A .fea path, fea.Study object, or fea.Sweep object. |
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.validate works
- Exactly one
.feapath,fea.Study, orfea.Sweepinput is required. Direct integer and resident numeric inputs have no role and reject before document resolution. - Study validation returns validity, issue codes/details, and an evidence path. Sweep validation additionally returns per-study entries. These public results contain logical and text data rather than numeric measurements.
- Validation does not execute the solver or a numeric provider. Existing typed, STL-backed, or synthetic geometry does not intrinsically require native OCCT; resolving topology-bearing CAD from a path may require its configured importer.
Example
Validate before solving
validation = fea.validate(study);
assert(validation.valid);Using fea.validate with coding agents
Open a RunMat example with live inputs, then ask the agent to explain how fea.validate changes the result.
Run a small fea.validate example, explain the result, then change one input and compare the output.
FAQ
Does validation allocate solver results?⌄
No. It checks the study or sweep and records evidence without planning or solving.
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.sweep · fea.trends
Open-source implementation
Unlike proprietary runtimes, every RunMat function is open-source. Read exactly how fea.validate is executed, line by line, in Rust.
- View the source for fea.validate 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.