





I explained compound corners, and Claude updated the Python scripts to detect them automatically. It's looking at throttle between WOT, lat g changing direction, corner apex latitude/longitude coordinates which I copied off Google Maps, and figuring out which corners are separated by straights, vs. which ones flow together. I can analyze multiple corners together (in this case, T1 - T5). The blue bands are my top 10% through the selected corners, green is best lap through that section (last October), red is the lap I'm analyzing (this weekend).
The bottom Δt panel shows two views. Dotted = pure pace (laps aligned by distance traveled, so line choice doesn't count). Orange = total time gap. The shaded gap between them is how much time I lost because of the line I took. I tried plotting the lines on a map but the GPS error is too much. I can go look at the videos from these laps to get a reference.
The main thing I'm enjoying is how it's now a lot easier to paste this screenshot into Claude and discuss my driving inputs / results, vs. trying to work with the raw CSV data.
Car is a base 981 Cayman, data is CSV exports from TrackAddict with OBD and GPS receivers. This is a personal project, I don't intend to launch this as a site.
I was able to rotate the car as I got off the brakes (kind of), but I was waiting too long to unwind the wheel and get back on throttle. A couple of ridealongs with instructors gave me a better idea of how to get my Cayman to continue turning, shifting the weight to the back, balance, all of that. I'm not really doing much of it in this lap, but I'm happy I now have a skill to work on to try and get out of my rut. T6 and T14 are where I feel I wait the longest to get back on power.
No, this isn't available as a SaaS with a paid subscription :)
I'm trying to do something (hopefully) different from the apps I see. My goal here is to be able to compare a recent session against all my previous sessions and see what I did differently. Here's a WIP example screenshot. I have the Ridge built out for now. I can select a corner, the app shows me the speed / throttle / etc. for my best time through the corner as well as top 10% band, and I can pick individual sessions / laps to view alongside that. For those who aren't familiar with the Ridge - T6 is a long left hand sweeper, I've been trying to double-apex it (carry more speed in / brake harder and deeper) which you can see, but then I over-slowed and also waited longer than I needed to get back on throttle. Suspension and tires should actually have more grip now vs. the March 2025 lap.
Took more work than I expected to clean up the data, as you all warned me. My main takeaway is that a Bluetooth GPS dongle isn't accurate enough for analyzing lines. But combining that + speed and driven distance from the OBD + some corner apex lat / long coordinates from Google Maps, I think I have a workable model of the track, and I've filtered out the sessions which were wet, or had so much traffic that no corner was close to pace, or the GPS data seemed too far off, etc.
I've been wanting to extract my lap data into something I can feed into ChatGPT / Claude and ask it questions. For example, "What's my fastest through T11 at the Ridge, vs. what do I usually do?" I use TrackAddict - it lets me see sector / lap times and compare 2 laps at a time, but I haven't found anything that will let me look at one corner across multiple laps / sessions. And I want the information in a format I can throw at an LLM and ask what patterns it notices.
I have around 50 sessions at the Ridge over 4 years. The raw TrackAddict CSV files are too much data for AI to handle, especially if I want to load multiple sessions. I have a GPS and OBD sensor so there are about 20 rows per second / 30 columns per row. A lot of that is at full throttle which isn't really relevant. So I've been thinking of writing some scripts that would bring this down to a more manageable size and focus on the interesting data. My current idea is to extract per corner data - where I got off throttle, where I got on / off brake (guessed from G force data, my car doesn't emit brake position over OBD), entry speed, min speed, apex speed, exit speed, time through the corner, which way my car was pointing, things like that. This should be a lot less information than the raw sensor data from the entire session. And then I could have an LLM analyze those files and have a discussion.
I'm very specifically not trying to create an "AI lap analyzer / optimizer" - I already have the Garmin Catalyst, and I don't want a fixed analysis. My goal is to get the data in a form that I can use with a chatbot.
Does this approach make sense? And before I start vibe coding a bunch of scripts, are there tools out there already that do this?