Why the Data Gap Is Killing Your Strategy
Look: you’ve got the lap times, the pit windows, the glossy charts — but you’re missing the raw, unfiltered marathon of tyre wear that decides who’s on the podium and who’s stuck in the gravel.
What “Long Runs” Really Mean
Here is the deal: a long run isn’t just a 30-lap stint; it’s the brutal, 70-plus kilometer grind where the rubber softens, the temperature spikes, and the compound’s life expectancy collapses like a house of cards.
Collecting the Numbers
First, grab the telemetry from every sector – pressure, temperature, slip angle – for each lap after the 10-lap warm-up. Then, overlay the weather feed. If the ambient hits 30 °C, you’ll see a 0.02 °C per lap rise in tyre core. That’s the sweet spot for predictive modelling.
Why Most Teams Miss the Mark
And here is why: they treat the data like a spreadsheet of averages, not a living organism. They smooth it, they filter out the “outliers” that are actually the critical signals of tyre degradation spikes. The result? A strategy that’s always a lap late.
Turning Raw Data into Action
Take the lap-by-lap drop in grip – 0.3 seconds per lap after lap 20 – and feed it into a simple exponential decay model. The model spits out the optimal pit window at lap 27, not the conventional lap 30 you’ve been told to trust.
Practical Tools You Can Use Right Now
Grab an open-source data logger, hook it to the car’s ECU, and dump the CSV. In Python, a quick np.polyfit on pressure vs. lap number gives you the degradation curve. No fancy AI needed.
Real-World Example
Last season, a mid-grid team used the practice long runs tyre data from a wet-to-dry transition and shifted the pit stop by just three seconds. They vaulted from 12th to 6th. Three seconds. That’s the power of raw numbers.
Final Actionable Advice
Stop polishing the data. Dump the averages. Load the lap-by-lap wear, fit the decay, and tell your engineers to pit when the grip loss hits 0.5 seconds per lap – no more, no less.