dAPEX
Well-Known Member
- Joined
- Nov 27, 2024
- Threads
- 3
- Messages
- 70
- Reaction score
- 36
- Location
- Kansas City, MO
- Car(s)
- 2024 Supra 3.0 6 MT, 2015 BMW m235i 6 MT, 1999 BMW M3 5-speed, 2013 BMW X3 35i
Very cool!Yeah i very likely will. It started off as something i wanted for myself. I didn't want to put something out that did not make accurate/logical conclusions with context, and had enough reasoning built into it to hold back when confidence levels did no meet a certain threshold. Which necessitated a confidence threshold framework...lol you see where this is going. I think i've gone down the rabbit hole far enough at this point that i think i'm probably going to release something in the not too distant future. Web and probably app
Bryan that's amazing, and in many ways, VERY similar to what i'm working on.
I can see some subtle differences. You seem to be a bit more data viz focused, and i think i'm more data viz plus analysis focused. The analysis part is essentially where i've been spending 90% of the time, because it's also largely platform dependent obviously. So each platform (e.g. B58, EJ257 etc...) is basically like an entirely separate and standalone product that requires it's own massive reasoning framework. Different rules, thresholds, failure points etc...Those frameworks, considering the time investment required to build them, would create a very safe moat over time.
The reason i see the analysis part as essential is because i think it's not just time consuming, but something just way too hard to spot certain essential things in the data ourselves. Some of that is sorted by making sure the right charts/graphs are in place, but that doesn't help debug some tune issues for example.
You're also lap focused. (what you're doing there looks amazing btw)...and i actually do have something like that in the pipeline. But i want to invest more time into the analysis framework before going that direction. Depth over breadth at this point, basically. The amount of up-skilling i've had to do....oof. But i'm nothing if not obsessive.
just as an example, and i know i'm not saying anything you don't know, just explaining my thought process. Took the below screenshot from one of your pics. I've built so many contextualization rules before drawing any such conclusions:
E.g. was the temp recorded a spike or sustained? What was the Ambient temp + IAT delta? No ambient temp shared since it's not logged...then assume 10 seconds pre WOT temp to represent ambient here (if certain other conditions are met). Vehicle speed / airflow to understand if we're looking a heat soak vs actual cooling system limitations. I'm oversimplifying it basically, but i'm trying to explain where a lot of my time has been invested.
I've also been building a mod recommendation engine to alongside the log analysis. Of course that would be predicated on the log user including what basic mods they've already done (e.g. intake manifold, catless DP etc...). Another massive framework of rules. Didn't mention this earlier, because this isn't the meat and potatoes, but i def see this as a strong magnet. Thousands of lines of types of rules across a number of tabs i've lost count of by now. By platform of course. The layering of triggers and thresholds is what protects the recommendation engine from making silly recommendations
I would've said let's just combine forces and maybe even take this seriously (esp since if my reading is correct, and going by the color palette you're using alone, you have a creative background, and i have a generalist + specialist performance marketing/analytics one) but you might be even more misanthropic that me haha. Well, at least online.
Sponsored
