Quote:
Originally Posted by beez
...
Data can tell you lots of stuff, but there's also many things it can't... things that only a good coach in the right seat can see and feel... like visual scanning, smoothness, anticipation, H&T skills, braking (too early, too late, over slowing the car), carrying momentum through corners, and probably most important - car balance... how balanced is the car at turn in, apex and exit, and how does that effect the car's momentum on corner exit.
|
I agree with most but not all of this, many of these things CAN be seen with data, for example braking, momentum, and car balance can be easily seen with data. With wheelspeed data (most current cars with data connected with CAN have independent wheelspeed from all four corners), and then (optionally) adding steering wheel angle sensor, you can chart yaw.
Add syncrhonized video, and you can see exactly what the data is showing you (or vice versa, see something on the video and you can go see what this 'does' to the data).
Sure it's easy for a coach to spot this stuff, esp. if there are significant issues, but a ridealong coach isn't always possible for various reasons, and there are always sessions where you will be running solo.
Data has been the first mod I made to my first two race cars (Pi in my RS America and Motec in my 996 Cup), and my 997 Cup came with Motec, so I've had data in all three of my race cars. I have synchronized Chasecam in both the Cups.
Since I don't have a right seat, the vast majority of coaching I get from others is from analysis of video and data. Mostly video - they'll watch the video and point things out etc. I'll then go look at the data to make sure I fully understand exactly what's going on etc. I of course do much more self-analysis of data than I get in third-party analysis also.
Sometimes I'm lucky enough to be able to get video and/or data from a top pro driver in a similar car at the same track, so being able to analyze properly is very helpful.
Data does take a while to understand and to be able to fully use. Just like I never pass up an opportunity for someone to watch my video/data and give me tips, I never pass up an opportunity to see how someone else uses data.
I'm apparently different from Mooty - he wants to know how to go faster without needing to know all the details. I'm the opposite, I want to know all the gory details about what's going on with the car. Someone can say 'ease off the brakes earlier in turn 2', and I'll immediately want to go look at brake and longitudinal G traces to see what's happening under braking in 2 versus other corners, look at the synced video to see where exactly I'm easing off, etc.
Data allows me to do lots of self-coaching. I usually know exactly where that last little bit of time is, and it's usually not in technique. I usually know intellectually where I can carry more speed, but my foot doesn't always agree, and sometimes insists on lifting even when I'm telling it to stay planted :-) Or carries the brakes a little long even when I go I can carry a little more speed into that super-fast corner :-)
My rule #1 on data is to have it working reliably, along with video, and record every session, always. When I don't have a lot of time, the first thing I'll do is look at a trace of my fast lap of a session, versus my previous fast lap at that track (sometimes I'm faster, sometimes I'm slower) and look to see where the differences are (in Motec this is 'Show Variance'). If I'm picking up time somewhere, this tells me I made a good change, and to keep doing it. If I'm losing time somewhere, it tells me that I used to be better than I am now. I'll then look at other laps from the session compared to the fast lap, to see if there are common places where I often (but not always) lose time. This shows where I CAN be fast, but am not always as consistent as I need to be.
Of course, I'm at a different place than many, I'm usually looking for tenths of a second. I'm racing not DE, and I'm naturally both competitive and analytical. I like to be on pole, and if I'm not on pole I'm not far off, so I'm likely not making significant mistakes or driving errors.
One other thing that data does is let me quickly see that the car is working properly. Fuel pressure and battery voltage and fuel usage and speed at the end of the straight etc. etc. all let me see that I'm not starting to have fuel system or electrical or engine power problems that might become more severe. Also very helpful in diagnosis - I had a flakey fuel system problem and data let me 'prove' to the shop that wanted to replace some particular parts that it couldn't possibly have been those parts (I had two separate fuel pumps, and data showed that I had a problem on one side and not another, so common systems could not have been the problem). Turned out to be a collapsing hose between the cell and one of the pumps, after some swapping of pieces and data analysis discounted any other reasonable hypothesis.