|
|
|
|
|
by Someone
3062 days ago
|
|
"their reasoning that they must ignore stationary objects to avoid too many false positives sounds pretty reasonable to me" I don't understand your logic. Stationary objects either are rare, and wouldn't trigger too many false positives, or they aren't, and the car should be prepared for them. |
|
I think the problem with this is to set them into the correct context. Around the road (and thus in the visible field of the sensors) you have A LOT of stationary objects such as houses, trees, traffic signs, roadside objects, parked cars, ... I think there is probably a big challenge determining which of these objects might be in the way and how to correctly ract to them.
Just as an example: Considering the situation the article and enhancing it a bit with guessings, it would have been the right decision to either stop or change lanes (depending on the road). However, if the car decides to change lanes and there is traffic on the other lane, we are in the same trouble of an accident due to autopilot again. Also, if autopilot decides to change lanes (or something similar in the category of "driving around") on a one-lane road (maybe even with missing lane marks), we might end up in oncoming traffic. Or what happens if the system falsely applies the decision to break in a turn with roadside objects (think of a 90° turn with a house in the corner). If the car falsely applies an emergency break here, our hypothetical car might be the one smashed into. Also, how do you set the thresholds for "stationary". If it is set too low, we might not stop infront of a stationary object until it is too late, if we set it too hight, we might stop way too early, say, in a traffic jam, again being the ones provoking accidents or more traffic jam due to unforseen heavy breaking.