Fast company logo
|
advertisement

As part of its ongoing investigation into the deadly Arizona crash between a self-driving Uber vehicle and a pedestrian, the company has found that though the car’s sensors detected the pedestrian, the car’s software was too slow to react, reports the Information. Specifically, the software designed to decide how it should react to objects in […]

Uber finds that its software was likely responsible for deadly collision

[Photo: freestocks-photos/Pixabay]

BY Michael Grothaus

As part of its ongoing investigation into the deadly Arizona crash between a self-driving Uber vehicle and a pedestrian, the company has found that though the car’s sensors detected the pedestrian, the car’s software was too slow to react, reports the Information. Specifically, the software designed to decide how it should react to objects in its path took too long to decide because it was tuned too far in favor of ignoring objects that could be “false positives.”

False positives are usually things like plastic shopping bags, which a self-driving vehicle could hit without doing any damage. Uber’s internal report also noted the human test driver behind the wheel was not paying close enough attention before the collision. It’s important to note that the official NTSB investigation into the deadly collision is ongoing and Uber’s report is only preliminary.

advertisement

Recognize your brand’s excellence by applying to this year’s Brands That Matter Awards before the early-rate deadline, May 3.

CoDesign Newsletter logo
The latest innovations in design brought to you every weekday.
Privacy Policy

ABOUT THE AUTHOR

Michael Grothaus is a novelist and author. He has written for Fast Company since 2013, where he's interviewed some of the tech industry’s most prominent leaders and writes about everything from Apple and artificial intelligence to the effects of technology on individuals and society. More


Explore Topics