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 direct + RK4 solvers
- SI units
- Canonical cases verified
- Release 1.1.1
Mission
Make the path from equation to result legible.
VehicleLab is 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
VehicleLab 1.1.1
Half Car · 4 DOF is the flagship Studio model, with coupled heave and pitch, explicit front and rear axle roads, and separate front and rear suspension parameters. Quarter Car · 2 DOF remains a simpler reference model. Both support Transient and Frequency Study and Compare plus Transient Explore.
Transient Study and Compare can show a Model schematic or contextual 3D Vehicle Motion. Completed Transient Study can export a local wide or vertical engineering video. Motion uses completed numerical evidence; mirrored wheels and local axle roads are visual context, not independent corners or a reconstructed spatial road.
Study, Explore, and Compare share a clear engineering path. Deterministic runs produce completed evidence for interpretation, exact-channel CSV, per-plot PNG, and one persistent Engineering Report action. Portable projects store definitions only; importing one requires a new run. Journey remembers explored capabilities separately from engineering and project state. The public V&V evidence includes one source-audited quarter-car numerical benchmark; it does not establish measured production-vehicle correlation.
Current limitations
Narrow by design
Parameters are generic and uncorrelated. There are no calculated full-car dynamics, roll, independent corners, 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.