Also the collision-detection systems should be getting tested so that they improve too. You want your fall back systems to be more reliable than the regular system. So if you turn off the collision-detection systems never fix the false positives and false negatives then you'll always have these problems.
> At very least I would want to add code to recognize these special braking events and then I would need to test this code... which of course would be impossible to do in simulation
Why? Does Volvos system raise events differently in context? I would imagine it's pretty simple to simulate an event by driving the car into a wall and capturing a dump of the CAN bus.
The autonomous system could take the Volvo system firing as an event like anything else that it needs to reconcile in the system. If anything the autonomous system could be used to improve Volvo's system by capturing extensive data dumps of the events leading up to misfire events.
I have no idea how this input would be interpreted by an autonomous driving system. However if I was designing such a system I would be pretty concerned about the potential safety impact. At very least I would want to add code to recognize these special braking events and then I would need to test this code... which of course would be impossible to do in simulation because Volvo’s system is probably closed source and likely exists as a hardware black box. At the end of the day I would probably be more comfortable designing my own collision avoidance system than relying on one that I couldn’t test easily, and that might spit unexpected inputs into my already-complex system.
So no, I don’t see this is a simple question of “adding redundancy”. I think what Uber did here probably makes good sense. The fact that their own collision-avoidance systems didn’t fire is, however, a problem.