Slashdot Mirror
Philosophical Differences In Autonomous Car Tech
An anonymous reader writes: The Guardian has an in-depth article on the status of self-driving car development at BMW. The technology can handle the autobahn just fine, for the most part. But the article highlights philosophical differences in how various companies are developing self-driving tech. European and Asian car manufacturers are fine working on it piece-by-piece. The car will drive itself when it can, but they expect drivers to always be monitoring the situation and ready to take control. Google's tests have taught it otherwise — even after being told it's a prototype, new drivers immediately place a lot more trust in the car than they should. They turn their attention away and stop looking at the road for much longer than is safe. This makes Google think autonomous cars need an all-or-nothing approach. Conversely, BMW feels that incremental progress is the only way to go. They also expect cars to start carrying "black boxes" that will help crash investigators figure out exactly what caused an accident.
In related news, Google is bringing on John Krafcik as the CEO of its self-driving car project. He has worked in product development for Ford, he was the CEO of Hyundai North America, and most recently he was president of Truecar.
Expecting a driver to take control in a failure scenario is not a solution.
Why not, that is the design philosophy for airliners made in the past 30 years and their pilots who operate them. Sit and babysit the machine for 99.99% of the time; then jump in ready to go for the 0.01% of the time the situation is beyond the programming of the software. (In which case the software 1) does wrong thing. 2) just shuts-down while displaying a message to the pilots to let them know that, suddenly, THEY are flying the plane.)
The problem with this is that when an airline pilot is forced to take control, they probably have MINUTES before any real issue will arise.
They are asking car drivers to take over when there are possible issues within SECONDS (possibly less).