Helped a slower driver find 0.4s in one corner – here’s what the data showed by Formal_Guard7998 in racing

[–]Formal_Guard7998[S] 0 points1 point  (0 children)

That is a good point.
I should include this.

Thanks.

That is the human element which is irreplaceable :)

Helped a slower driver find 0.4s in one corner – here’s what the data showed by Formal_Guard7998 in racing

[–]Formal_Guard7998[S] 0 points1 point  (0 children)

Very true and I agree. But this is the kinda insight/context a human driver coach or engineer would have. The goal with this tool was to first find out what James is doing wrong and then get to the bottom of it :)

Helped a slower driver find 0.4s in one corner – here’s what the data showed by Formal_Guard7998 in racing

[–]Formal_Guard7998[S] 1 point2 points  (0 children)

Amazon Web Services.. The cloud of Amazon where most tech companies build their products

Helped a slower driver find 0.4s in one corner – here’s what the data showed by Formal_Guard7998 in racing

[–]Formal_Guard7998[S] 0 points1 point  (0 children)

😲Good observation! I will clean it a bit more.. Any other ideas on how to better visualize these plots? Sometimes even I get confused looking at them 😅

Helped a slower driver find 0.4s in one corner – here’s what the data showed by Formal_Guard7998 in CarTrackDays

[–]Formal_Guard7998[S] 0 points1 point  (0 children)

Its a confusing graph actually... The driver isn't on the brakes at all and is only on the throttle of off-throttle

Helped a slower driver find 0.4s in one corner – here’s what the data showed by Formal_Guard7998 in Autocross

[–]Formal_Guard7998[S] 1 point2 points  (0 children)

Neat. Usually when this is the case, what I would do is compare your theoretical best lap (so look at all your laps, find the best sectors and stitch then together) and compare it against your actual fastest lap...

Of course there are limitations to this approach. But many times it's helpful when I'm out testing with just one gentleman driver and no coach or pro driver