3 ms·
Right, but as the article mentions, each time it got reclassified, the tracking history gets wiped, so the car doesn't know that the object is about to enter th
by Sohcahtoa82 7y ago
Right, but as the article mentions, each time it got reclassified, the tracking history gets wiped, so the car doesn't know that the object is about to enter the path of the SUV. It just sees an object that's in the other lane and assumes it's going to stay there.
- SilasX 7y agoMajor facepalm right there. It's like all the stupidity of UI choices I see, but with the consequence of a car collision, and (in cases like this) death.
- dkonofalski 7y ago>the tracking history gets wiped This might be a little too nitpicky but it doesn't get wiped. It's simply no longer associated with that object because it's considered a different object. It's still a huge, glaring issue, obviously, but all the data is still there. In this particular case, the "object" was identified as one type of object and so all of the data related to that was classified as "car" info, for example, and then, when it's reclassified, that additional data starts recording to the "bike" info bucket. The software should have been keeping track of certain data regardless of that classification but it's only seeing the latest bucket of data. If the tracking history got wiped, we wouldn't have the data to look back on to see how this was all happening.