One completed record, one coherent report
Export Engineering Report appears only after VehicleLab has an authoritative completed Study, ComparisonRecord, or SweepRecord. The browser builds a structured vehiclelab.report.v1 model, renders professional plots from its stored arrays, lays out an A4 PDF, and downloads it locally. No report content is sent to a backend.
If inputs are edited afterward, the visible completed record remains immutable and the Studio asks for a rerun. A report exported before that rerun describes the visible completed configuration; it never combines old results with edited-but-unrun simulation inputs.
What each report contains
Study
Project objective and notes, exact quarter-car configuration, road, initial conditions, numerical setup, existing metrics, four response plots, provenance, and limitations.
Compare
Baseline, Variant A, shared scenario, changed physical parameters, stored neutral metric deltas, five overlay plots, provenance, and limitations.
Explore
Sweep range, candidate count and ordering, deterministic candidate table, optional selected candidate, four response plots, and one acceleration/travel trade-off plot.
Reliable plot architecture
uPlot remains the responsive interactive chart. PNG and PDF figures use a separate deterministic Canvas2D renderer driven by the same completed numerical arrays. The renderer draws axes, tick labels, units, grid, zero reference, legends, line styles, actual curves, discrete Explore markers, and selected-candidate emphasis at 1600 × 1000.
Export never resimulates, resamples, smooths, normalizes, filters, or interpolates result values. Explore markers are discrete engineering evaluations; VehicleLab does not imply a continuous response surface or optimum.
Artifact responsibilities
| Artifact | Meaning |
|---|---|
| Project JSON | Reproducible definition - what to run again. |
| CSV | Raw numerical output - what was computed. |
| PNG | Professional engineering figure from authoritative arrays. |
| Review-ready evidence with context, results, provenance, and boundaries. |
Project schema vehiclelab.project.v1 remains definition-only. Reports have the independent vehiclelab.report.v1 identity and do not change model 0.2.0, solver 0.1.0, or evidence 0.4.0.
Evidence boundary
A report is not an engineering recommendation.
VehicleLab reports configuration and deterministic evidence neutrally. It does not identify a winner, certify a design, claim OEM approval, imply production-vehicle correlation, or turn the Zhao numerical reproduction into physical validation.