fea.material — Create typed RunMat FEA material data.
fea.material(id, Name, Value, ...) creates mechanical material data with optional thermal, acoustic, electrical, and plastic models.
Syntax
material = fea.material(id, Name, Value, ...)Inputs
| Name | Type | Required | Default | Description |
|---|---|---|---|---|
id | StringScalar | Yes | — | Material id. |
Name, Value | Any | Variadic | — | Mechanical, thermal, acoustic, electrical, and plastic material fields. |
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.material works
- The material id is exact text and the optional name defaults to that id.
- Finite real numeric material fields accept all eight built-in integer classes and remain exact until one host-only binary64 model-storage conversion, so sufficiently wide integers can round.
- Mechanical, thermal, acoustic, electrical, plastic, and electrical frequency-response numeric fields share this boundary.
- Required fields, nested model shape, finiteness, and unknown fields are validated before the material object is returned; resident numeric fields are rejected.
Example
Create a structural material
steel = fea.material("steel", "YoungsModulusPa", int64(200000000000), "PoissonRatio", 0.30);Using fea.material with coding agents
Open a RunMat example with live inputs, then ask the agent to explain how fea.material changes the result.
Run a small fea.material example, explain the result, then change one input and compare the output.
FAQ
Are material properties stored in their input integer class?⌄
No. Integers remain exact through argument parsing and then enter the analysis model's binary64 physical-property fields once.
Related Fea functions
fea.boundaryCondition · fea.compare · fea.domain · fea.field · fea.interface · fea.loadCase · fea.materialAssignment · fea.model · fea.plan · fea.plot · fea.results · 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.material is executed, line by line, in Rust.
- View the source for fea.material 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.