VehicleLabLaunch Studio
Menu

Verification & Validation / Evidence

Road & Traversal numerical evidence

Independent RD001–RD010 procedural road excitation checks, exact RK4 stage coverage and Full-Car equivalence, with explicit limits on physical correlation.

Road → Traversal → Excitation → Full-Car

VehicleLab 1.5.0 exposes the previously verified procedural Road/Traversal engine. Road/Traversal milestone 1.5.0-alpha.2 and derivation vehiclelab.road-to-corner-excitation v0.1.0 remain unchanged. A straight forward constant-speed path locates nominal tire contacts; absolute road elevations become datum-relative inputs to the existing linear passive Full-Car model.

The reference cases use independently coded formulas and geometry. Every sampled elevation equals its reference exactly (maximum absolute error 0 m). RD002 records a 0.75 s axle delay for a 3 m wheelbase at 4 m/s. These are numerical verification results, not external vehicle or road-test correlation.

CaseScenarioIndependent acceptance
RD001Flat roadAbsolute elevation at all four contacts
RD002Full-width raised cosineIndependent waveform and wheelbase/speed axle delay
RD003Left-only featurePositive road t supports the left wheel tracks
RD004Lateral offsetShifted traversal changes support membership
RD005Speed scalingDoubled speed halves encounter duration with unchanged amplitude
RD006Signed negative featureNegative amplitude and exact baseline return
RD007Periodic sineIndependent elevation formula at every contact
RD008Boundaries and holdsExact feature endpoints, start/end and endpoint holds
RD009Unequal geometryIndependent front/rear axle-arm and track offsets
RD010DeterminismRepeated Float64 bytes, provenance and corner ordering

Full-Car bridge and evidence transport

Flat road at its own datum gives exact zero response from zero state. Symmetric full-width cases give exact zero roll; a left feature gives the verified positive left-side-up initial roll. All 34 complete result channels agree with equivalent prescribed temporal inputs, including the non-divisible final step. The representation-only acceptance bound remains 1e-12; the recorded equivalence case has zero error.

The excitation schedule covers every literal RK4 start, midpoint and end-stage request, including the final short step, without nearest-sample matching. Direct and browser Worker runs preserve all Float64 arrays, 16 metrics and provenance exactly. All 39 distinct result/excitation buffers transfer once and detach at the sender.

Display and physical evidence boundaries

A stationary, capped display mesh evaluates the same procedural road but never supplies solver input. Completed response interpolation and traversal use one playback clock. Cameras, display gain and body artwork cannot change numerical evidence.

Only flat, raised-cosine and sine surfaces, with full-width or finite raised-cosine lateral support, are available. No road-file or OpenCRG/OpenDRIVE/OpenSCENARIO ingestion, stochastic standards, steering, yaw, lateral or longitudinal dynamics, calibrated tire radius/spin, tire contact/enveloping/slip, nonlinear suspension or active control is claimed. Physical correlation has not been performed. Spatial project persistence and Full-Car video, Compare, Explore and Frequency remain unavailable.

Configure Full-Car sources and Drive over Road Motion · Full-Car numerical evidence · Evidence boundaries