Guide¶
How the pieces fit, and why they are the way they are.
This is an alpha release. It has been checked against known
cases, not yet against a broad set of tests; numbers it produces are
to be verified by independent means before anything depends on them.
The application says so when it opens, and asks for that to be
acknowledged every time. Anything that looks wrong is worth
reporting to [email protected]. The project file, .vdyn,
is provisional: the next alpha will save projects in the Engineering
Sciences Common Data Format (.escdf), a public standard, and will
still open .vdyn files; the first release that is not an alpha will
not. Open each .vdyn once in that alpha and save it again.
- Projects, links, and the Basis — the structure everything else reads
- The project tree — what a selection shows: one object, records picked in one, or several together
- The objects — every kind of object, what it holds, and what can be done with it
- Units — SI inside, display units at the boundary
- Plotting — every plot the app draws, from code
- The modal workflow — the app and a script, step for step
- How the mode fitting works — the algorithm, and how it differs from the classical batch methods
- The random vibration workflow — a controller run in, a compliance report out
- The transient workflow — a target waveform against what the article did
- The shock workflow — events, the SRS, and its tolerance band
- The sine sweep workflow — tones tracked through a sweep, against what was asked for
- The system identification workflow — a plant measured, and how well
- The wavelet reading — a time history as a scalogram
- The channel table — the one object that is a spreadsheet, and its rules
- How a PSD means its area — bandwidth, integration, and what the numbers mean
- Reports — symbolic bindings, live text, one file out
For signatures see the API reference in the site navigation; for the
design decisions behind all of it, PLAN.md in the repository root
is the long form.