Lap time and delta analysis

From Formula One Wiki
Jump to navigation Jump to search

Lap time analysis decomposes a lap into distance-aligned events and state variables (speed, longitudinal/lateral acceleration, throttle/brake, gear) to attribute time gains and losses to specific driver inputs, tyre states, aerodynamic conditions, and traffic effects. The goal is a quantitative, reproducible explanation of delta-time traces, enabling strategy and setup decisions (brake bias, aero level, tyre plan, shift maps).

Data channels and sampling[edit | edit source]

Recommended minimum channels (100–500 Hz acquisition, 50–100 Hz processing):

  • Vehicle speed (km/h) and distance (m)
  • Longitudinal / lateral acceleration (g)
  • Brake pressure (bar), throttle (%), steering angle (°)
  • Gear, engine speed (rpm), rear-axle power estimate (kW)
  • GPS position (lat/lon) → projected centreline abscissa s (m)
  • Tyre inner/middle/outer IR (°C) where permitted
  • Ride heights or aero platform proxy (if available)

Distance alignment and rolling delta[edit | edit source]

Analysis must compare laps on a common distance axis (not time) to preserve causality through braking/accel phases.

Curvilinear abscissa (distance)

Rolling delta (cumulative time difference) For two laps A (reference) and B (candidate), integrate the local time step over distance:

This yields the familiar continuous “time-gain/time-loss” trace engineers use to pinpoint where a lap diverges (brake point, minimum-speed, exit). A practical workflow is: (i) compute s from GPS/speed, (ii) resample all channels on s (e.g., 1 m), (iii) form , (iv) annotate corner entries/apices/exits, (v) attribute deltas.

Corner phase metrics[edit | edit source]

Define corner regions by decel/steer thresholds and apex index . Report phase metrics lap-to-lap:

Metric Definition (distance domain) Typical F1 range
Entry speed at first brake-on 220–320 km/h
Minimum speed 60–180 km/h
Brake zone length 80–160 m
Exit delta @150 m ±0.05–0.25 s
Lateral peak (filtered) 3.5–5.5 g

Physics back-bone (friction ellipse & power)[edit | edit source]

Friction-ellipse constraint (per tyre) maps combined usage: so braking deep (high ) reduces available lateral and sets the attainable entry/rotation trade-off. Longitudinal acceleration is power-limited at high speed: governing straight-line delta growth when one lap has higher deployment or lower drag.

Fuel and mass sensitivity[edit | edit source]

A first-order lap-time penalty with fuel mass: Use per-sector sensitivity when fuel burn is uneven (e.g., long WOT sectors).

Tyre degradation imprint on delta[edit | edit source]

Represent compound-specific degradation as convex in age a (laps since stop): calibrated from long-run pace. A typical (illustrative) prior:

Compound \alpha_c (s/lap) \beta_c (s/lap²) Nominal stint (laps)
C1 0.015 0.00018 25–35
C3 0.025 0.00035 16–24
C5 0.035 0.00070 8–15

Tie this to carcass/bulk temperatures via a window penalty if you track IR channels.

Sector attribution (worked method)[edit | edit source]

1) Compute and mark sector endpoints .

2) Sector deltas are differences of the cumulative curve: .

3) Within a corner, split phase deltas by integrating only over the corresponding s intervals (entry / mid / exit).

4) Attribute mechanisms by co-evaluating traces and, where available, power and platform proxies.

Example comparison (same car, two laps)

Item Lap A (ref) Lap B Comment
Tlap (s) 88.420 88.205 B faster −0.215 s
S1 delta (s) −0.090 Later brake, same Vmin
S2 delta (s) −0.055 Higher exit accel (deployment)
S3 delta (s) −0.070 Lower drag in final straight
Min speed T9 (km/h) 146 144 B slower at apex, but better exit
Exit delta @150 m (s) −0.060 Time gained after apex

Traffic/dirty air correction (optional)[edit | edit source]

When comparing laps with different traffic states, incorporate a penalty term: where inside a user-defined “close-following” gap (dirty-air zone), and when DRS is active. Calibrate from multi-lap data (typ. 0.15–0.60 s/lap impact in prolonged following; DRS gain 0.10–0.30 s/lap depending on zones).

Statistical modelling & validation[edit | edit source]

  • Back-to-back deltas: same stint, same traffic → isolates driver inputs.
  • Regression on distance grid: fit on covariates to quantify marginal effects.
  • Optimum-lap synthesis: compare observed to minimum-time solution (QSS/optimal control) to reveal theoretical headroom.
  • Tooling: most pro suites provide rolling best/“theoretical best” from micro-sectors using distance alignment.

Minimum-time benchmarks (for context)[edit | edit source]

Quasi-steady-state (QSS) and optimal-control solvers produce reference speed/acceleration profiles under tyre-load and power limits. These are invaluable to test whether an observed delta stems from sub-optimal inputs or hard constraints (power, drag, μ). See surveys and theses for reproducible formulations and open data.

Practical checklist[edit | edit source]

  • Align on distance, not time.
  • Inspect , brake, throttle, around every apex.
  • Quantify entry (brake point & decel), rotation (Vmin), exit (accel to +150 m).
  • Separate fuel, tyre age, deployment state, and traffic before blaming driver.
  • Validate conclusions against a minimum-time or “theoretical best” lap.

References[edit | edit source]