Find where the time went.

Racing compares two runs and shows where the time changed, with the evidence beside every explanation. Today it runs on one synthetic Jerez session in your private workspace.

Request access Invited sign-in

Run B against run A

Jerez · Fictional GT4 #27 · Speed (km/h) · Lap distance (m), sector 2

Synthetic scenario

Median lap delta: +0.780s
A02 / B02 · sector 2: +0.580s

Reading the chart

Run A, A02: Reference lap from run A. Front roll bar at position 3.
Run B, B02: Compared lap from run B. Front roll bar moved to position 4.
Corner window: 2100 to 2800 m. The window the evidence cites.

View speed data as a table

Speed every 100 m through the corner window, read from the chart samples and rounded to the nearest km/h.
Distance (m)	Run A, A02 (km/h)	Run B, B02 (km/h)
2000	166	166
2100	166	166
2200	166	163
2300	131	127
2400	75	73
2500	75	73
2600	131	127
2700	167	163
2800	167	167

Figure 1. The shipped comparison, drawn from the synthetic Jerez scenario samples.Representative laps stay separate from run medians.

What Racing does today

Five steps, all shipped, all running on the synthetic Jerez scenario. None of them needs a telemetry upload.

Compare the runs: a median over the laps you keep for each run, plus one representative lap per run for the traces.
Exclude a lap you judge unrepresentative, such as B03 through traffic, and the run medians update. The representative traces stay fixed.
Inspect speed, throttle and brake through the sector 2 corner window, labelled so an explanation can cite it.
Read competing driving and setup hypotheses, then correct the context and request a revised analysis. Earlier results keep their source revision.
Save the next test: one change, what to hold constant, the measurement, the success criterion and when to stop.

Every explanation cites its evidence.

Hypotheses link back to the exact window in the traces. Missing measurements, such as hot tyre pressures in the synthetic session, are listed as missing and never filled with a zero.

Engineering judgment remains yours. A test distinguishes explanations; it does not promise a gain.

Engineer’s debrief

AI-generated, advisory

Evidence, competing explanations, and a test to separate them.

Driving explanation

Run B lifts earlier and returns to throttle later through the corner window, which may explain the slower exit.

B02 corner window
A02 corner window

Setup explanation

The front roll bar moved from position 3 to 4 in run B, which may add entry understeer. These traces alone cannot establish the cause.

Run B context
Run A context

What remains uncertain

Hot tyre pressures were not measured in either run. Adding them as context would narrow the setup explanation.

Missing evidence

Hot tyre pressures, run A
Hot tyre pressures, run B

Proposed next test

Repeat before changing the car

Hold the setup fixed. Repeat run A's lift and throttle cue on clean laps. Compare the corner window and run medians.

Example wording from the synthetic scenario, not a live AI result.

The method behind the comparison

Racing applies the rules a careful engineer applies by hand. How to compare two stints fairly covers lap selection and medians. Driving or setup: separating causes covers reading the traces.

Design-partner roadmap, 2027 season

Planned with design-partner teams for the 2027 season. Not available today.

MoTeC and AiM CSV import, so your own logged sessions enter this same comparison.
A per-team isolated model trained only on that team's data. No cross-team training and no shared model.
Team data stays the team's, with export and deletion when a team leaves.

See the comparison on your own screen.

Private early access. Start with the synthetic Jerez session in a private workspace.

Request access