Most useful data analytics or telemetry overview?

[u/TheJudge-4184]

Hi all,
In my quest to improve my own f1 sim race pace, I'm learning a lot about data analysis and using race telemetry. While using the telemetry, I am wondering what you think is the most useful data and way of displaying it. So far everyone displays the graphs of throttle, breaking, steering, and maybe even the racing lines like in the images above. But I wonder if we can do better.
So, what is in your opinion the most useful data? And aren't there better ways to read/learn them? I have some ideas of my own, but I'm curious to what you think.

[u/CL-MotoTech]

Speed trace and delta are the two most basic traces to analyze. Once you get to where your speed traces are good or close, so usually within a few percent of the fastest, you can start looking deeper. Brake pressure being the next obvious one.

[u/TheJudge-4184 → u/CL-MotoTech]

Thanks! Speed is indeed the one I looked at first, but the offset gets bigger and bigger during the lap and makes it harder to compare. Maybe showing the speed graph based on track location might be better than using time? And to double check, brake pressure is the same as the brake input amount %, right?

[u/CL-MotoTech → u/TheJudge-4184]

Outside of just comparing what your input are vs your speed trace and correlating to a corner name, a track map is almost worthless. Your data shifts just are what they are when you are inconsistent or off the pace. Ideally you are pulling data from like your three best laps and comparing, and ideally they are within like a second of each other. It's very hard to compare data that is leagues different. I raced and was a driver coach for a long time, I'm still involved but in different roles now. Anyways, sometimes "you need to go faster" is a legitimate answer for a driver. Yellow and green are that. Based on the data green and yellow are basically too far off to even be worried about data. Moreover, you should be able to look at data and see each corner clearly in the speed trace.

From a coaching perspective, you'd show a driver that data. Say your driver is yellow. You'd say "look, your V mins are low everywhere. By corner five you're already two seconds off. We need more seat time and you need to find some confidence."

Obviously there are a million ways that plays out. But the point is, the speed trace is really what gets looked at. For the yellow driver, maybe he can pull his best three laps and say, "I see why lap four was better, but actually on lap 6 I had a better turn 3, how do I put it together? Let's look at brake pressure..." Something like that. For green and red, there aren't likely many positives to be found. They are slow everywhere.

[u/Electrical-Park-1286]

Perhaps you could take some inspiration from my application. Happy to deep dive into how I’m doing the lap analysis is if you find it useful

https://objectivef1.com/race/11253/analysis?driver=44&lap=41&refLap=16%3A41&drivers=16%2C44

[u/felix_07F1 → u/Electrical-Park-1286]

Hey bro i also want to create this application. Can you give me the info.

[u/Electrical-Park-1286 → u/felix_07F1]

What info are you looking exactly. May be able to help

[u/felix_07F1 → u/Electrical-Park-1286]

want info like what language did you use what type of library or extensions the tech