Yahoo Autos Cruise Knew Its Robotaxis Struggled To Detect Children But Still Kept Them On The Road
Things aren’t going so well for General Motors’ autonomous Cruise division right now. After a human driver hit a pedestrian, a robotaxi pinned her to the ground, and it later came out that the Cruise taxi actually dragged her for 20 feet before stopping. Understandably, California then banned Cruise from operating in San Francisco. As it turns out, though, Cruise had way more problems than just that one incident. Allegedly, it also knew its robotaxis were a danger to children but still kept them on the road, the Intercept reports.
Internal materials reviewed by the Intercept show that Cruise knew its autonomous vehicles struggled to detect children and wouldn’t drive more cautiously when they were nearby. One safety assessment literally even said, “Cruise AVs may not exercise additional care around children.” The company also knew it needed “the ability to distinguish children from adults so we can display additional caution around children.”
Read more
That's The End Of Activision Blizzard's $120 Million Overwatch League
Marvel's Kevin Feige Teases When to Expect the X-Men In the MCU
Starfield's Controversial Missing PC Feature Arrives In New Update
Our Picks For Link, Ganon, And More In The Live-Action Zelda Movie
Apparently, Cruise also struggles to detect holes in the ground and there was a good chance one of its robotaxis would drive right into a pit that it encountered. So it didn’t just have problems detecting children. To get those details, head over to the Intercept and read the whole story there.
More from Jalopnik
Steven Spielberg and Tom Hanks take to the skies in the Masters Of The Air teaser
Google Asks Regulators to Liberate Apple's Blue Text Bubbles
Suicide Squad Publisher Promises Even More Live-Service Games
Sign up for Jalopnik's Newsletter. For the latest news, Facebook, Twitter and Instagram.
