API reference¶
The guides cover the common paths; the complete, generated API for every public item lives here:
- Rust API →
rustdoc for thedynarscrate. - Python API →
pdoc for thedynarspackage.
Rust¶
Add the crate and pick the features you need:
| Feature | Enables |
|---|---|
| (default) | parsing, navigation, validation, d3plot / binout readers |
signal |
result-history signal processing (SAE J211 CFC, Butterworth, integrate/differentiate) and injury criteria |
ffi |
C ABI (and, through it, Fortran) bindings for the parse + validate path |
typed-keywords |
a generated typed struct per keyword (~3170; opt-in) |
Python¶
The published wheels bundle the signal feature, so filtering and injury
criteria are available out of the box. import dynars exposes the core at the
top level — parse_deck, Workspace, Rule, D3plot, Binout — with
post-processing grouped into submodules: signal processing under
dynars.signal (cfc, butterworth, integrate, …), occupant injury criteria
under dynars.injury (hic36, resultant, clip, …), and the keyword-name
constants under dynars.kw.
Keywords dynars doesn't ship¶
The built-in library covers thousands of LS-DYNA keywords. For a vendor, newer, or otherwise unlisted keyword, describe its card layout once and get the same typed, columnar access: