Professional Motorsport Data Analysis: Step 6: Apply Changes and Test
Watch This Course
$197 USD $98.50 USD
-OR-
Or
8 easy payments of only $12.31
Instant access. Easy checkout. No fees.
Step 6: Apply Changes and Test
02.36
| 00:00 | - The next step after we've gone through all of our analysis is to implement everything for the next run. |
| 00:05 | This process will be different depending on whether you're a one man band and you're doing your own data analysis for your own driving or you're an engineer working with another driver. |
| 00:13 | I recommend starting with a maximum of 3 specific sections of track to work on at once. |
| 00:17 | Any more than 3 tends to be a bit much to take in for the average driver. |
| 00:21 | If you're working with someone less experienced maybe you can reduce that even to 2 or even 1 thing, just really to give them the opportunity to concentrate on 1 thing at a time or maybe only 2 things at a time within a lap, otherwise it can be a little bit overwhelming, it can be quite a lot of information to go through. |
| 00:37 | this is one area where having done a track walk prior to the event is going to come in really handy. |
| 00:41 | If you're an engineer working with a driver, that's going to help you guys understand what references you've got on track, you're going to have a better understanding of knowing where a certain curbs starts or ends or where a tree is or where a break in the fence or whatever it is you're using for references, this is where you can start to build that common language around discussing braking markers, braking markers are probably going to be one of the main things you're looking at when it comes to logged data analysis between a pro and an am. |
| 01:05 | One of the things I find really useful when I'm working with a driver is to get them to repeat back to me what we're going to work on for that run. |
| 01:10 | So obviously we would have talked about this outside of the car, we would have gone through the data in detail together, I would have shown them what was going on, where they're losing the time and then we would have summarised them into those points and then once they're in the car and they're all strapped back in again, I'll generally get them to repeat back to me what we're going to work on just to make sure they remember exactly what they're going to do and make sure we're going to focus on the right things. |
| 01:31 | So at this point, you're ready to send them back on track and for now, for the rest of the test session or your race day, whatever you're doing, this is really just a case of rinse and repeat, this same cycle goes over and over. |
| 01:41 | You come in, you download the car, you check the reliability, you're going to check the driver inputs, you're going to check what's happening with the chassis, you're can discuss it and make the changes you need to make, whether that's a setup change or whether that's a change to the way the car's being driven and you're going to send them out and you're going to try and improve on it again and again. |
| 01:56 | Now I recommend keeping your runs relatively short if you're there on an open test day, rather than just running around continuously and wearing the car out, using lots of fuel, lots of tyres, I prefer to keep the runs relatively short, maybe a maximum or 3, 4, 5 flying laps maximum at a time. |
| 02:13 | The idea here is that you go out, try and improve what you're working on, come back and check the data and sort of repeat that process as many times as you can. |
| 02:21 | Again I need to reiterate here, it doesn't matter what car or what logging system you're working with, this process is going to be generally applicable regardless. |
| 02:28 | It doesn't matter if you're not using a MoTeC system, hopefully you guys can see how generically applicable this process is. |
