RunMat
  • Pricing
RunMat
GitHub
GitHub
DownloadSign InTry in Browser
DesktopRuntimeServer
RunMat

Run math blazing fast

GitHubX (Twitter)LinkedIn

Company

  • About
  • Pricing
  • Contact
  • License
  • Privacy

Learn

  • Docs
  • Blog
  • Benchmarks
  • RunMat vs MATLAB Online

Get product updates and release notes from the RunMat team.

© 2026 Dystr · Made withfor the scientific community.

RunMat™ is a registered trademark of Dystr, Inc. MATLAB® is a registered trademark of The MathWorks, Inc. RunMat is not affiliated with, endorsed by, or sponsored by The MathWorks, Inc.

/
See all docs
Builtin Reference
    • 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
    • fea.validate

fea.runOptions — Create family-specific typed FEA run options.

fea.runOptions(solver, Name, Value, ...) creates a fea.RunOptions object whose schema is selected by the solver family.

Syntax

options = fea.runOptions(solver, Name, Value, ...)

Inputs

NameTypeRequiredDefaultDescription
solverStringScalarYes—FEA solver family.
Name, ValueAnyVariadic—Family-specific structural, tolerance, timing, precision, and quality options.

Returns

NameTypeDescription
resultAnyFEA object or operation result.

Errors

IdentifierWhenMessage
RunMat:fea:LoadFailedA .fea document cannot be read, parsed, or resolved.fea: failed to load FEA document
RunMat:fea:InvalidInputA builtin receives an unsupported argument pattern or object type.fea: invalid input
RunMat:fea:OperationFailedA validation, planning, run, result-query, comparison, or trend operation fails.fea: operation failed
RunMat:fea:InternalAn FEA object or operation result cannot be converted to a RunMat value.fea: internal error

How fea.runOptions works

  • Supported solver families are linear_static, modal, acoustic, thermal, transient, cfd, cht, fsi, nonlinear, and electromagnetic.
  • Count and iteration fields are nonnegative exact structural scalars at construction. All eight integer classes and ordinary integral doubles are accepted exactly; fractional, nonfinite, negative, out-of-range, nonscalar, and resident controls reject. Solver-specific positivity checks run before execution.
  • Tolerance, time, scale, ratio, exponent, frequency, and residual fields are real physical scalars. Integer inputs cross once into binary64 after kind, field, and scalar-shape validation; solver-specific finiteness and range checks run before execution.
  • Logical controls require logical scalars. PrecisionMode, PreconditionerMode, QualityPolicy, PrepArtifactId, and PrepCalibrationProfile are text. Public PrepContext injection is rejected because prep context is internal runtime state.
  • Unknown or duplicate normalized options reject before object construction. Structural option properties remain exact typed integers; true floating options remain double.

Example

Configure an exact transient step count

opts = fea.runOptions("transient", "StepCount", uint32(20), "TimeStepS", 5e-4);

Using fea.runOptions with coding agents

Open a RunMat example with live inputs, then ask the agent to explain how fea.runOptions changes the result.

Run a small fea.runOptions example, explain the result, then change one input and compare the output.

FAQ

Why is an integer accepted for a tolerance?⌄

It is accepted as a finite real scalar and converted once to the option's binary64 physics field; count fields instead remain exact integers.

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.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.runOptions is executed, line by line, in Rust.

  • View the source for fea.runOptions 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.

Getting started · Benchmarks · Pricing

Download RunMat

Download RunMat for full performance, or use RunMat in your browser for zero setup.

Download RunMatOpen Sandbox
On this page
  • Syntax
  • Inputs
  • Returns
  • Errors
  • How fea.runOptions works
  • Example
  • Configure an exact transient step count
  • Using fea.runOptions with coding agents
  • FAQ
  • Related Fea functions
  • Open-source implementation
  • About RunMat