About / Product mission
Engineering software should show its working.
VehicleLab explores how transparent, browser-based tools can make vehicle-dynamics models easier to inspect, run, question, and validate.
- Runs locally
- No simulation data uploaded
- Deterministic RK4
- SI units
- Canonical cases verified
- Release 0.6.0
Mission
Make the path from equation to result legible.
VehicleLab is being developed as an engineering application where users can understand a model’s force balance, configure its assumptions, execute it without installing a specialist desktop stack, and inspect numerical evidence alongside the response.
Browser delivery matters because it reduces setup friction. Transparency matters because accessibility without visible equations, conventions, and limits can create false confidence.
Product principles
Rules for the current product.
- 01
Explain before amplifying
Present the model and its meaning before using visual output to build confidence.
- 02
Keep context near results
Units, signs, assumptions, and limitations belong close to the quantities they shape.
- 03
Compute locally by default
Deterministic browser execution keeps the current study responsive and private.
- 04
Make evidence visible
Validation is part of the product experience rather than a hidden implementation detail.
- 05
Earn model complexity
Add capability only when a testable engineering reason justifies it.
Current status
Release 0.6.0
The working product supports a linear passive quarter-car ride study, four prescribed road inputs, deterministic RK4 integration, bounded damping/stiffness parameter sweeps, neutral trade-off plots, candidate promotion into one Baseline/Variant A comparison, synchronized overlays, optional display-only SVG motion playback, and one traceable published passive quarter-car numerical benchmark. Portable project definitions, exact-channel CSV, provenance JSON, reliable per-plot PNG, and professional PDF Engineering Report exports remain local to the browser.
Current limitations
Narrow by design
Parameters are generic and uncorrelated. There is no full-car motion, handling, nonlinear hardware, controller, cloud project library, autosave, account system, DOCX generator, or server-side solver.
Future direction
Broaden only with evidence.
Future model, workflow, and comparison capabilities may be explored when they have a clear engineering purpose, explicit assumptions, stable data contracts, and validation cases. This is a direction—not a claim that those features are committed or complete.