I want to really learn to read data. Where do I start?
#1
Tour de Franzia
Thread Starter
iTrader: (6)
Join Date: Jun 2006
Location: Republic of Dallas
Posts: 29,085
Total Cats: 375
I want to really learn to read data. Where do I start?
I have a G2X and I've been using it for a few years now. After talking to a pro-type-guy I race in TT with, I realized that I should focus on data and learn more to go faster.
I see some poor braking at the 32 and 95 second marks (not progressive, elevation is constant in these locations) on the fastest lap looking at "Accel G". In general I think my braking force/trail braking looks good; coming on progressively without stomping the pedal, trailing off evenly (32-second mark increases brake pressure since we transition up-hill). I found that I could build pressure more slowly to make more total braking force and slow the car faster (comparing accelG in "distance", MPH in distance, and MPH in time).
I don't really know what to make of the Lateral G graph and I think it's too track specific to give-away much data for people who don't know the track.
Aside from that, I think it looks like a pretty good lap which tells me I'm wrong because no one is paying me to drive cars around racetracks. Is there anything that stands out on this file which is nasty? I'm open to any discussion on this because I'm totally ignorant.
Thanks.
I see some poor braking at the 32 and 95 second marks (not progressive, elevation is constant in these locations) on the fastest lap looking at "Accel G". In general I think my braking force/trail braking looks good; coming on progressively without stomping the pedal, trailing off evenly (32-second mark increases brake pressure since we transition up-hill). I found that I could build pressure more slowly to make more total braking force and slow the car faster (comparing accelG in "distance", MPH in distance, and MPH in time).
I don't really know what to make of the Lateral G graph and I think it's too track specific to give-away much data for people who don't know the track.
Aside from that, I think it looks like a pretty good lap which tells me I'm wrong because no one is paying me to drive cars around racetracks. Is there anything that stands out on this file which is nasty? I'm open to any discussion on this because I'm totally ignorant.
Thanks.
#4
Former Vendor
iTrader: (31)
Join Date: Nov 2006
Location: Sunnyvale, CA
Posts: 15,442
Total Cats: 2,100
Start with a Garmin 810.
Real answer: Have someone faster drive your car and then overlay the speed traces in "Segment X" mode. Easy way to see exactly where you are sucking. Moving past that point probably requires that you spend some time attending a seminar or other training session on the software and/or spend money on $ensor$.
Real answer: Have someone faster drive your car and then overlay the speed traces in "Segment X" mode. Easy way to see exactly where you are sucking. Moving past that point probably requires that you spend some time attending a seminar or other training session on the software and/or spend money on $ensor$.
#5
Elite Member
iTrader: (2)
Join Date: Sep 2008
Location: Central Florida
Posts: 2,799
Total Cats: 179
I tend to think of the data as similar to a dyno, but more complex.
That is, it's value tends to come in the comparisons - either in your lap times, in predictive lap times, or in comparing your laps vs someone else's laps. For the latter, preferably someone else in your car or - barring that - someone else in a comparable car using the same data acquisition.
At least, that's what I've gleaned from people who actually know what they are talking about. I have been lucky enough to be around a lot of those kinds of people over the past couple of decades.
That is, it's value tends to come in the comparisons - either in your lap times, in predictive lap times, or in comparing your laps vs someone else's laps. For the latter, preferably someone else in your car or - barring that - someone else in a comparable car using the same data acquisition.
At least, that's what I've gleaned from people who actually know what they are talking about. I have been lucky enough to be around a lot of those kinds of people over the past couple of decades.
#10
Are you trying to use the data logger to make you faster or to make the car faster. You look at the data in different ways. Video is better for the, "oh look I **** up there constantly factor." Where accelerometers, shock pots, and pyrometers are better for figuring out how to make the car faster. Chris Brown's book is good in general. But if you want the car faster bits you need the chassis dynamics and mechanics knowledge to know what the squiggling line from your shock pots mean. I haven't graduated past using the data for more than seeing where I screwed up and coming up with an optimal time, oh course only getting 3-7 shots at a track to get it right plays into that.
#11
I've got a decent amount of experience driving and looking at data, but comparing your data with someone else who is faster in the same car is by far the most valuable info you can get.
On our Grand AM cars we have all the fancy sensors and inputs/outputs datalogged (yaw rate, brake pressure, inverse corner radius, steering wheel angle, etc. etc. etc.) but none of them help nearly as much as just overlaying two speed traces. Comparing my sorry, pathetic excuse for driving with a "real" pro in the same exact car, that is how I have learned to go faster. We use the data from the other sensors to try to improve the car, but for improving the amatuer drivers, it's mostly just looking at the speed traces versus the pro.
All of my experience is with Traqmate and Race Technology so I can't really give any input on specifics with the Racepak, sorry.
#12
This.
I've got a decent amount of experience driving and looking at data, but comparing your data with someone else who is faster in the same car is by far the most valuable info you can get.
On our Grand AM cars we have all the fancy sensors and inputs/outputs datalogged (yaw rate, brake pressure, inverse corner radius, steering wheel angle, etc. etc. etc.) but none of them help nearly as much as just overlaying two speed traces. Comparing my sorry, pathetic excuse for driving with a "real" pro in the same exact car, that is how I have learned to go faster. We use the data from the other sensors to try to improve the car, but for improving the amatuer drivers, it's mostly just looking at the speed traces versus the pro.
All of my experience is with Traqmate and Race Technology so I can't really give any input on specifics with the Racepak, sorry.
I've got a decent amount of experience driving and looking at data, but comparing your data with someone else who is faster in the same car is by far the most valuable info you can get.
On our Grand AM cars we have all the fancy sensors and inputs/outputs datalogged (yaw rate, brake pressure, inverse corner radius, steering wheel angle, etc. etc. etc.) but none of them help nearly as much as just overlaying two speed traces. Comparing my sorry, pathetic excuse for driving with a "real" pro in the same exact car, that is how I have learned to go faster. We use the data from the other sensors to try to improve the car, but for improving the amatuer drivers, it's mostly just looking at the speed traces versus the pro.
All of my experience is with Traqmate and Race Technology so I can't really give any input on specifics with the Racepak, sorry.
#13
Tour de Franzia
Thread Starter
iTrader: (6)
Join Date: Jun 2006
Location: Republic of Dallas
Posts: 29,085
Total Cats: 375
Making Sense of Squiggly Lines: Christopher Brown: 9780983259312: Amazon.com: Books
I saw a recommendation for this book, now I need decent data acquisition.
I saw a recommendation for this book, now I need decent data acquisition.
I'm trying to make the driver faster, not the car. The car is as perfect as it will ever be.
Thread
Thread Starter
Forum
Replies
Last Post
stoves
Suspension, Brakes, Drivetrain
5
04-21-2016 03:00 PM