Data Analysis Fundamentals: Step 6: Apply Changes
Watch This Course
$129 USD $64.50 USD
-OR-
Or
8 easy payments of only $8.06
Instant access. Easy checkout. No fees.
Step 6: Apply Changes
02.47
| 00:00 | - So the last step in our 6 step process is to go through and apply the changes that we've learned based off analysing the logged data. |
| 00:06 | As I mentioned before, you generally want to keep the number of things you want to work on each run to a minimum. |
| 00:12 | I personally find 3 things is the maximum number of things I want to work on with a driver. |
| 00:17 | Now it will depend on whether you are the driver and you're doing this analysis for yourself or whether you're an engineer working with your driver. |
| 00:23 | If you're working with a less experienced driver, you may actually want to reduce the number of things you're working on even more. |
| 00:29 | If you're starting with someone with not as much experience on track and certainly isn't used to taking feedback based on their logged data, maybe it's just one or even two things at once that you want to work on. |
| 00:38 | You're much better to go and head out on track with a well defined plan rather than trying to work and fix everything at once. |
| 00:44 | So if you've gone through and done a track walk already before the event started, this is one of the places that it's going to start to pay dividends because you're going to have a much better idea of the references you've got on track. |
| 00:54 | So when you're talking about particularly things like brake markers and turning in points, having those references that you've already gone through, looked at slowly and calmly on track, whether it's marks on the track or changes in the seal or maybe a mark on a wall, these are the kinds of things that are really useful when you're discussing different reference points on track as far as how far you're going to move your reference point each point, if we're doing something like extending your brake marker. |
| 01:18 | One of the tricks that I find is quite useful as an engineer if I'm working with a driver is to, after we've gone through and debriefed exactly the changes we want to make, once I get them sat back in the car and strapped in, before we head back out onto the track, I'll get them to repeat back to me the things that we're working on. |
| 01:32 | That just makes me sure that they know the parts that we're concentrating on and make sure we're on the same page. |
| 01:38 | In the hustle and bustle of it all it is quite easy to get flustered and get lost so I do find that after getting them back in the car and before we head back out on that track to get another run in, get them to repeat back the things to you, the parts of the track they're going to work on and what they're going to work on in this run. |
| 01:53 | So I find when you're going through and working on driver technique, it does pay to keep the runs relatively short. |
| 01:59 | Rather than going out and banging around all day and just wearing out your car, your tyres and your brakes, my preference is to keep the runs quite short. |
| 02:05 | So on your average length racetrack, I'm usually trying to do flying laps, maybe three, four flying laps at a time with an in and an out lap on the end of each of those, come in and regularly download the data and debrief it with your driver, going through it regularly, trying to make steady incremented changes as we go rather than staying out for a long time and just banging around and wearing the car out. |
| 02:26 | So hopefully after going through that worked example, that's clear to most of you that it's not going to matter too much if you've got a different logger and car combination than what we've used in today's worked example. |
| 02:36 | Hopefully the concepts of logging and organising and analysing your data are going to be clear, particularly after going through the course body itself. |
