fea.results — Query a persisted RunMat FEA run for post-processing.
fea.results(runOrRunId, Name, Value, ...) returns a fea.Results object for a persisted run. Passing an existing fea.Results object without options returns that object.
Syntax
results = fea.results(runOrRunId, Name, Value, ...)Inputs
| Name | Type | Required | Default | Description |
|---|---|---|---|---|
runOrRunId | Any | Yes | — | Persisted run id, fea.RunResult, or fea.Results object. |
Name, Value | Any | Variadic | — | Field, diagnostic, one-based mode/snapshot selector, and inclusion 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.results works
- The required first input is a persisted run-id text scalar, a single-run
fea.RunResult, or an existingfea.Resultsobject. A sweep result must be queried through one of its per-study run ids. FieldsorIncludeFieldsandDiagnosticCodesaccept text scalars, string arrays, or cells of text. Inclusion flags accept logical scalars or exact numeric zero and one; other numeric values and resident controls are rejected before artifact lookup.ModeIndicesandTransientSnapshotIndicesare positive, one-based exact structural vectors. All eight integer classes and ordinary integral doubles are accepted; zero, negative, fractional, nonfinite, out-of-range, matrix-shaped, and resident selectors are rejected before artifact lookup.- Omitted field and diagnostic lists mean no filtering. Omitted mode and snapshot selectors include every available item. Inclusion flags default to true.
- Field values, frequencies, times, residuals, rates, ratios, and other physics quantities retain binary64 representation. Shapes, element/component counts, byte sizes, mode/snapshot indexes, iteration counts, fingerprints, and other structural metadata remain exact typed integers.
- The query and argument-decoding path is host-side and performs no provider gather. Stored device references are returned as metadata rather than executed. Persisted results do not intrinsically require native OCCT.
Options
FieldsorIncludeFields: field-id text list; default empty.IncludeFieldValuesorFieldValues: logical or exact numeric 0/1; default true.IncludeDiagnostics: logical or exact numeric 0/1; default true.DiagnosticCodes: diagnostic-code text list; default empty.IncludeModalResults: logical or exact numeric 0/1; default true.ModeIndices: positive one-based exact structural vector; default empty.IncludeTransientResults: logical or exact numeric 0/1; default true.TransientSnapshotIndices: positive one-based exact structural vector; default empty.IncludeNonlinearResults: logical or exact numeric 0/1; default true.IncludeElectromagneticResults: logical or exact numeric 0/1; default true.
Example
Select the first and third modes
results = fea.results(run, "ModeIndices", uint64([1 3]), "IncludeDiagnostics", false);Using fea.results with coding agents
Open a RunMat example with live inputs, then ask the agent to explain how fea.results changes the result.
Run a small fea.results example, explain the result, then change one input and compare the output.
FAQ
Are result indexes zero-based?⌄
No. The RunMat scripting builtin accepts and exposes one-based mode and snapshot indexes; the internal host operation translates them to its storage representation.
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.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.results is executed, line by line, in Rust.
- View the source for fea.results 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.