How to quickly and easily find speed from data traces

J.G.
By J.G. Pasterjak
Aug 11, 2024 | data, Lap Times, Data Traces | Posted in News and Notes | Never miss an article

Photography Credit: Chris Tropea

All the squiggly lines in the world mean nothing if you’re not taking the time to decipher them and turn that info into a plan.

Who has time to analyze all that data? Not many of us, that’s who. 

But you can find time with even the quickest of glances and the simplest of data systems. Don’t let data overload convince you that every trace needs to be agonizingly pored over to extract some gains. For many drivers who don’t live at the ragged edge of ability 100% of the time, there’s plenty of low-hanging fruit to be picked with a fast review.

How to approach that? The first thing you’ll want to look at is a speed/distance graph. Honestly, even if all you ever log is a speed/distance graph, you can glean a ton of info from just that simple trace. 

At first glance, a speed/distance graph should look like a series of up and down squiggles. The vertical axis represents speed and the horizontal axis shows distance, so it makes sense that the car accelerates down straights, slows for the corners, then accelerates back out down the next straight. The progression of the plot should be climb (accelerate), dive (braking), climb (accelerating out of the subsequent corner) and repeat.

Find the Flats

A flat line is a massive red flag and should be the first thing you tackle when trying to analyze data at a glance. Eliminating them will pay huge dividends as you stay on the gas longer or brake later–or, ideally, both. 

  • Look for flat, horizontal areas on the speed trace. These flat areas represent distance covered at a constant speed, and there’d better be a darn good explanation for why the car isn’t accelerating or braking. 
  • A horizontal area, though, can show up in extremely long, constant-radius corners–like, beyond 180 degrees. 
  • Flat areas can also show up in very long autocross slaloms where you’re constantly transitioning several times before accelerating out of the obstacle. 
  • Flat lines are frequently a hallmark of a novice driver or someone learning a track–nothing to be ashamed of–and can show up toward the end of straights or, more precisely, preceding braking areas. Ideally, you should accelerate until the moment you brake, but unfamiliarity or uncertainty can lift that foot off the throttle before the braking zone. 
  • Mid-corner flats are also common in similar situations of unsure conditions or abilities. Ideally, the car should decelerate all the way to the minimum cornering speed–typically at the apex of the corner–where the throttle is picked up for corner exit. A mid-corner flat usually means straight-line braking, followed by steady cornering, followed by acceleration once the car is fully pointed toward the next corner.

Sharpen the Peaks

Next, sharpen those peaks. The transitions from acceleration to braking should, in most cases, be razor sharp. Remember what we said earlier: If a car isn’t accelerating or braking, you’re leaving time on the table. 

  • The incoming trace should climb steadily and, depending on the speed of the straight in question, will either be fairly straight or have a steadily decreasing angle of attack. 
  • Powerful cars at lower speeds tend to have a fairly constant rate of acceleration, but rate of acceleration decreases as speed increases due to air resistance and gearing. So it’s natural to see your acceleration curves trail off as speeds go up. 
  • The goal here is to make that peak–the transition moment between acceleration and braking–as sharp as a knife. Anything that isn’t a sharp peak that instantly switches from up to down is lost time.
  • A peak that shallows out and levels off before dropping is indicative of a slow lift entering the braking zone before transitioning to brakes. 
  • A peak that rises steadily and then begins its drop with a rounded curve indicates brake initiation being too gentle before getting to max brake pressure.
  • ABS intervention and surface irregularities can introduce “noise” into the deceleration rate as well.

Analyze the Bottoms

Moving to the bottom of the graph, you’re also generally looking for sharp transitions as you switch from braking back to acceleration. Other factors, though, like the shape of the corner and amount of trail braking, can give these troughs a more gradual transition. So instead of simply looking for sharp valleys here, your lowest-hanging fruit will be lines that flatten or even reverse direction just before or–far more commonly–just after they bottom out.

  • Flattening prior to bottoming typically indicates braking that was initiated too early, then released, then reinitiated closer to the corner. 
  • Flattening after the bottom shows up quite often in the graphs of aggressive autocrossers, especially those who are just starting to make the transition to road course work. They’re getting to the throttle too early or too aggressively, needing to back out a bit, and then finally committing to full throttle. (While this technique sometimes gains a driver a tenth or two early in the corner exit, that adjustment closer to the final exit point nearly always costs speed down the subsequent straight.)
  • In a perfect and just world, your acceleration curve out of a corner should be ever climbing, and sometimes that means tempering your enthusiasm and delaying your throttle application until you can commit once and fully. An early throttle application is meaningless if it causes you to back off and lose momentum later in the cornering phase.
  • Your goal for the bottom of the curve: Maybe a slight reduction in rate of deceleration right at the end of the braking event due to trail braking, but the line should always be trending distinctly downward before transitioning back to the throttle and committing to acceleration out of the corner.

GRM+ subscribers get all sorts of benefits, including a 10% discount on their registration for the $2000 Challenge*. To save 10%, follow this link and use the code GRMplus2000 during checkout. *Maximum discount $30.

 

Join Free Join our community to easily find more data, Lap Times and Data Traces articles.
Comments
gunner (Forum Supporter)
gunner (Forum Supporter) GRM+ Memberand Dork
7/28/23 2:04 p.m.

Ah, this article will help me finally be able to interpret some of the squiggly lines during practice in assetto corsa. My climb from backmarker to mid pack is all but assured! (Insert evil maniacal laugh here)

MockingbirdRacing
MockingbirdRacing New Reader
7/28/23 2:28 p.m.

Wow this really helps understand the data trace. Just spent lunch looking at some recent laps and in the data can see where I left time along with every shift point and lift for curb bashing. Now I understand a bit more and can compare more than just lap times and entry and exit speeds. Thanks for the article.

AngryCorvair (Forum Supporter)
AngryCorvair (Forum Supporter) GRM+ Memberand MegaDork
8/1/23 12:10 p.m.

now i need a way to record data

and a running car to generate data

:-(

ETM
ETM None
8/4/23 1:50 a.m.

What other channels would you suggest to log besides speed and distance that could help detecting those mistakes and take advantage of those tenths of seconds needed to beat my fastest lap time? 

codrus (Forum Supporter)
codrus (Forum Supporter) GRM+ Memberand PowerDork
8/4/23 11:47 a.m.
ETM said:

What other channels would you suggest to log besides speed and distance that could help detecting those mistakes and take advantage of those tenths of seconds needed to beat my fastest lap time? 

IME, the speed trace over distance is the single most important data trace, you pretty much always start with this trace for identifying problem areas to focus in on.

The next tier of traces in importance are the driver inputs -- throttle position, brake pressure, and steering angle.  TPS is usually pretty easy to get on anything made in the last 30 years, and of the other two brake pressure is way more important than steering.  Once you've identified problem areas in the speed trace, you go to these traces (along with the accompanying video) to identify the reason for the problem.  Abrupt brake release, throttle too soon, throttle choppy, etc.

Pretty much every other trace after that is for addressing specialized problems.  If you've got a CAN bus car then getting engine data is usually pretty easy, and having temps, pressures, RPM, etc is nice if you're ever chasing an engine problem.  Wheel speeds are sometimes useful for understanding ABS or differential behaviour.  Ambient air temp is nice if you're comparing two runs from different days and want to see if that might account for power differences down the straight.

ShinnyGroove (Forum Supporter)
ShinnyGroove (Forum Supporter) Dork
8/4/23 12:02 p.m.

The real power with the data is if you csn compare your lap to a reference lap from a faster driver in the same car.  That is where throttle position and brake pressure channels are really useful.  Faster drivers usually brake later, brake less, and are on the throttle more. A time plot comparing your lap to the reference lap is nice; you can see specifically which parts of the course are costing you the most time. The other big thing is to get good video and integrate with data overlays if possible. Once you home in on a particular corner to improve, the video is a critical tool. 

JG Pasterjak
JG Pasterjak Production/Art Director
8/4/23 12:08 p.m.
ETM said:

What other channels would you suggest to log besides speed and distance that could help detecting those mistakes and take advantage of those tenths of seconds needed to beat my fastest lap time? 

Aside from a speed/distance, you can learn a lot from a friction circle, particularly about how you're transitioning from acceleration/braking into and out of corners. Just a quick glance at a G cloud will show you whether your trail braking or progressive throttling needs attention.

As for additional inputs, I'll agree with codrus on the throttle trace. Typically the throttle is going to match up pretty well with the speed trace, but you can find a bit more info, particularly from mid corner on, by looking at the throttle application.

Brake trace is also great, and arguably more important than throttle trace, but frequently harder to come by as a lot of ECUs don't give you easy acces to brake pressure readings. But if you have access to it, it's a great channel to add.

You'll need to log in to post.

Our Preferred Partners
9pxuF9kOofDUK8hD9GvcCjGt979UCwYTXLpFSrInXbM8yTWLKinhs06fvH8y3Xp0