If you learn to read one piece of data in your racing life, make it the speed trace: speed on the vertical axis, distance around the lap on the horizontal. Every logger produces one, every analysis package displays one, and a surprising amount of driving technique is legible in its shape alone.
The anatomy of one corner
Zoom into any corner and the trace draws a V (or a U):
- The cliff. A near-vertical drop where you brake. Steeper is generally better; braking is the one thing road cars and race cars alike do violently well.
- The bottom. Minimum speed, at or near the apex. This single number is the headline for the corner.
- The climb. Acceleration away. Its steepness tells you how early and how completely you got to power.
Two laps overlaid turn every difference into geometry: who braked later (cliff position), who carried more speed (bottom height), who exited harder (climb slope).
Four mistakes the trace exposes
- The early lift. The trace starts sagging before the cliff. The driver breathes off throttle approaching the braking zone, donating time before braking even begins. Very common, very tough to feel.
- Over-slowing. Your bottom is lower than the reference lap's. The classic amateur signature: entry feels committed, but the minimum speed says otherwise.
- The double apex that isn't. Two dips where the reference shows one. The car got slowed twice for a corner that needed it once, usually a line problem.
- The lazy climb. Bottoms match, but the reference climbs away harder. Throttle came later or more tentatively, and the gap compounds down the whole straight.
What the trace cannot tell you
The speed trace says a great deal about what happened and almost nothing about why. Over-slowed in Turn 3: was the line pinched? Braking release too abrupt? Confidence? The trace cannot say, and this is where channel-only analysis stalls, especially without a skilled engineer or coach to interrogate it.
Try asking 10 different people around the paddock what the same trace means. You'd be shocked by how many different answers you get. This is precisely where the knowing stops, and the guessing and rationalizing begins.
The fastest way to answer why is to watch the corner. Pair the trace with synchronized video and the over-slowing signature becomes a visible line choice; the lazy climb becomes a visible late commit. That pairing, numbers to locate and picture to explain, is the workflow GhostLap is built around, with sector analysis pointing you at the corner and the ghost overlay showing you the fix.
Learn the trace. Then let the video do the explaining. Request a demo to see both together on real laps.