Knightshade
Well-Known Member
If Tesla does not have some way to catch and log these failures, they will not be able to prioritize and make changes to prevent them in future updates. It is a flood of data, but some system to capture and catalog and evaluate these is essential to the success of FSD.
FWIW the way Tesla has historically done data capture for improvement was pushing campaigns to cars.... for example if the small test fleet that DOES have a report button (and tiny #s have reported they still do) found the system had trouble recognizing say a bicycle--- they'd send a campaign to the fleet "Send in clips of anything you think might be a bicycle with a chance of being a bike above X percent" and get back a ton of examples from different angles, in different conditions, etc... use labeling to sort bike and not-bike, and use that to train the system to better recognize bicycles.
(the other upside to this was they didn't care you had paid for FSD- or EAP or AP- all cars with the same sensors could collect the data)
It's certainly possible they're using geo-coordination of disengagement data to also look for trouble spots, that'd certainly make sense since all that data IS reported back every time (that you disengaged, where you did it, and how you did it)
I do agree that means there will be SOME really obscure cases they don't get because so few folks drive them... but offering the report button to a massive fleet was never a tenable option long term.