That being said, Toyota's (and Subaru's) approach is the smart way forward - add sensors and capabilities that augment the human, but leave the human always responsible and in control. In order for a crash to happen, the human AND the machine BOTH have to miss it.
Once the machine is good enough (and we figure out what "good enough" means), then it can take over driving. But not before.
That's the approach we know won't work. That was Tesla's first-round autopilot, the self-crashing car. The one that would happily run into obstacles protruding into a lane.[1][2][3] There are two big flaws with that approach. First, if it's good enough that people can tune out, they will tune out. Second, if the driver waits until the self-driving system has clearly made a mistake before taking over, they will be slower at reacting than if they were driving, and may be too late. See especially [3].
Volvo's CEO takes the position that if one of their cars crashes in self-driving mode, it's Volvo's fault. Urmson, while at Google, pointed out the first problem coming up even with their test drivers.
[1] https://www.youtube.com/watch?v=fc0yYJ8-Dyo [2] https://www.youtube.com/watch?v=DvRkSMCDX3o [3] https://www.youtube.com/watch?v=-2ml6sjk_8c
Tesla took the approach that the machine is in control and the human has to detect and take over when the machine makes a mistake. That is known to be a very problematic strategy, it's easy for the human to get distracted.
What Subaru has done is to leave the human in control, the machine only steps in when it sees a problem.
It's totally different safety outcomes. In fact, not even the same problem - one is "self driving", the other is "crash prevention".
But a car that can drive me while I sleep and become a Taxi while I work is something I would go into debt for.
I don't think most regular people will actually own fully autonomous cars to rent them out. Big players will do the capital expenditure to buy a fleet, and rent out transportation service. Renting in uber style will be basically the price of owning, but without the up-front capital expenditure, and it will provide the convenience of choosing the type of car for the specific transport needs of the moment. The margins of these rent-a-fleet services will be low, so you won't have a hope as individual car owner of actually buying a car and renting it out without turning it into a loss compared to just renting.
That's not really accurate. Tesla says the driver is ultimately responsible. That holds unless a court determines otherwise. The same is true for Toyota/Subaru. They're all SAE level 2 systems.
The opposite approach from this would be Waymo/Volvo who intend to take responsibility for decisions made by their vehicles. Those are SAE level 4 or 5 systems.
Only to those not familiar with autopilot systems in aircraft.
It's like the use of "hacker" - here on this site it still (probably) has most of it's original meaning. To the rest of the world it means a guy in a ski-mask with a russian/chinese accent who's after your bank account.
Unfortunately most of the world thinks pilots in commercial aircraft turn on the autopilot and can then go for a sleep, so when they see "Autopilot" on a Tesla, they think they can do the same.
They can go to sleep and the plane will continue to fly itself. However, if anyone found out they were sleeping heads would roll.
Autopilot electronics on a plane is trivial. Autopilot for a car is damn hard.
Isn’t that most people?
They can go for a sleep though.
The Pilot in Command is expected to sit in their seat and monitor the aircraft, surrounding airspace and the radios, and be ready to take control at a moments notice.
They can't go for a snooze without handing that over to another pilot first.
I think OP was talking about "crash avoidance" systems. Not systems that claim to drive the car but not really.
You're always driving, the car is just silently observing. If the car sees you're about to crash, it steps in and takes over. The opposite of Tesla's approach where you play the role of observer taking over when things go wrong.
The first approach is safe. The second approach isn't safe until full autonomy due to cognitive load and task switching delays.
What they don't do is take over steering. A last-second takeover of steering would make things worse some of the time.
http://www.leftlanenews.com/volvo-xc60s-collision-avoidance-...
I have a Honda. While its lane-keeping system won't steer during a crash, it definitely does steer to keep you centered in the lane (when it's able). That could help avoid all kinds of crashes due to inattentive lane-drifting.
Assuming for example the car is fitted with solid state lidar on the four corners and ESR on the four sides or even LIDAR.
What are your thoughts on crash prevention if the car has the same hardware as a a Waymo car?
(edit: to clarify, would you consider autosteering at the last minute safer than a human driver in that scenario?)
More like, if you are not a car on the left lane, then you are not. Bam, you got an accident.
Edit: Is the last video in the US? Is it normal for other drivers not to stop when they see an accident?
I wrote a previous YC posting on this, on why you need to use geometry first, then object recognition.
Seriously? All smartphones are video phones. I fail to see how they could be more widely used.
You may mean that people choose to make audio-only calls... but just because people choose to do that, it doesn't mean the technology isn't here & fully available in affordable, commercial, "good enough" form.
Autonomous driving is difficult primarily because of a changing world and low tolerance for mistakes. The state space of situations you're trying to map is just large. It will take time. But it's not even close to impossible.
Audio recognition is difficult for a different reason: language is difficult to disambiguate without context. So today the limits of our audio recognition bump up against knowing the context of words you're saying. It used to be the case that audio recognition had fundamental difficulties e.g at word boundaries but those challenges are mostly solved. Some of these challenges might not be solved without improvements in areas outside of the raw listening part of ASR.
> That being said, Toyota's (and Subaru's) approach is the smart way forward - add sensors and capabilities that augment the human, but leave the human always responsible and in control. In order for a crash to happen, the human AND the machine BOTH have to miss it.
This is your opinion. Folks at some other companies (e.g waymo) don't think this makes you safer. Human attention might not work the way you think it does.
Voice recognition is getting just barely tolerable. If you have tried to do something important using voice recognition you'd probably go bat shit crazy after a while. If it had the potential to kill people no sane human would allow it.
That is why I think self-driving cars and voice recognition are not comparable problems.
> Voice recognition also has a lot less market demand than self driving cars.
Just to expand on your point, today's 'self driving car' technology we may equal to where 'voice recognition technology' was 20 years ago. But 20 years ago, there is no incentive for industry to invest say $100 Billion in 'voice recognition technology', the benefits did not warrant such a huge investment. Where as'self driving car' technology there is potential to reap benefits that is why industry today investing $100 Billion ( all combined investments from all players )
> Technology can be invented that is decades ahead of other fields if enough money is invested.
> That is why I think self-driving cars and voice recognition are not comparable problems.
The huge economic value the can be created with perfected 'self driving car' is in the order of hundreds of Billions of dollars per year world wide combined . Here is an example scenario
In 2025 'self driving Electric Autonomous fleet' vehicles by Uber, Googles of the world offer 'miles plan' ( like our 2005 mobile monthly plan N minutes/month ) that is like 1000 miles per month you can hail any time for a monthly price of $300/month . This is huge economic value for at least 50% of USA drivers and people will embrace it.
Typical USA drivers total cost of ownership of CAR today is in the range of $400 to $600 per month ( CAR price + Repairs costs + car Insurance + gasoline cost) . This is with out counting 1.5 hours/day you have pay attention to drive, the time that can be used for other thing with autonomous fleet
I think
Wonderful.See that's where you're wrong. An autonomous vehicle doesn't have to have a human brain. It has to have very accurate sensors and classifiers tuned with generous safety params.
Like any vehicle it also needs redundancies for safety and sane default behavior (mostly "slam on the breaks").
Also, not "anything can happen." There are rules that govern the road that make this problem tractable. There are rules that govern physics that mean if you have adequate sensors + compute you can avoid hitting any objects at all, whether it's a person or otherwise. "Object x is 30 ft away with trajectory y, we're going 15mph, slam on the brakes."
The difficulties mostly lie in how we can "not slam on the brakes all the time and never make progress." e.g if you enter a construction zone you better know what to do and not just sit still, otherwise you'll never get anywhere.
Realistically speaking, even if Tesla or any other manufacturing company do get to that level of a "super advance Einstein-genius" self-driving car it will still be: "not even close" if it's riding alongside the highway with 18-year old Billy-bob speedster with a penchant for cutting lanes and living dangerously. Most car accidents are due to human error.
If all cars on the highway are self-driving cars, with the ability to learn and communicate with each other through mesh-network or what-not, with predictive capacity -- it will be a lot better than any driving human that can only see what's in front of them. We just need to get to that level where most cars on the highway are smart self-driving capable cars and we can build on top of that. No one should be relying on self-driving cars to do everything at this point in the game because we're not there yet.
We can't even get speech recognition right and meanwhile audio (sounds in general) aren't even being seriously considered for self-driving purposes, AFAICT.
For example, emergency response vehicles announce their arrival and direction often long before any visual contact is made. How will deaf autonomous cars recognize incoming emergency responders if the view is obstructed? Will they pull into the intersection just as a Fire Engine is running the red light?
Auditory input was deemed important enough that California even made it illegal to "wear a headset covering, earplugs in, or earphones covering, resting on, or inserted in, both ears" while driving just last year. [0] I suspect other jurisdictions have/will follow(ed) suit.
[0]http://leginfo.legislature.ca.gov/faces/codes_displaySection....
Reliably understanding speech is effectively strong AI. Humans don't speak very clearly, but we're spectacularly good at inferring meaning from context. Accurate transcripts of colloquial speech are often completely incomprehensible, because a vast amount of information is conveyed through context. When we're listening to someone speak, we're decoding the phonemes into symbols, but we're also constructing a model of the speaker's mind and predicting what they mean to say.
[0] https://www.scientificamerican.com/article/superpowers-for-t...
Yes, I've noticed this too. Sometimes you can almost see blue and red flashing lights on top of a police car.
si·ren (sīrən)noun 1.a device that makes a loud prolonged sound as a signal or warning.
Yes, if the driver is well trained. When I was firefighting and instructing drivers, we always emphasized that while the red light and siren gave you the right of way:
a. they don't absolve you of liability for a crash (at least under NC law)
and
b. if you get in a crash on the way to the scene, you're not doing anybody any good, PLUS you've now created another incident requiring another emergency response, PLUS another company (probably coming from further away) has to respond to the original call.
I can't speak for police, but firefighters are actually, in my experience, taught to be pretty conservative when it comes to running red lights, proceeding against traffic on one way streets, and other similar scenarios.
We also always used to emphasize "it does no good to get halfway there, real fast".
[0] https://www.enddd.org/end-distracted-driving/enddd-presentat...
[1] This web site's bona fides aren't clear, but its mission does not seem to specifically include advocating for the deaf, so there's no obvious reason for the information presented to be biased in favor of the deaf.
So why don't Siri/Alexa/etc developers give them context? I would LOVE to be able to say "Alexa, play playlist on shuffle mode" or even simple "Alexa, turn on shuffle and go to next song"
But no, the word "and" is completely off limits. Saying "shuffle playlist" instead of "play playlist" also doesn't work. I have to literally use 3 commands to do what I want:
"Alexa, play Taylor Swift" ... "Alexa, shuffle" ... "Alexa, next song"
With context, I could say "Alexa, play Taylor Swift on shuffle"
Apparently Siri is gaining the ability to deal with follow up questions in iOS11. Excited to try it out.
"Alexa, play Taylor Swift on shuffle"
vs
"Alexa, play Taylor Swift on Spotify" (real command)
I’m also ok sayin “Alexa, shuffle Taylor Swift” if that’s easier for their grammar.
As you mentioned, Alexa already understands shuffle (though I don't think it does for Spotify's integration).
That's not the only reason audio recognition is hard. If it were, audio recognition would be exactly as hard as interpreting written text.
> “Historically human beings have shown zero tolerance for injury or death caused by flaws in a machine,”
It doesn't matter if it's objectively safer; people have no issue doing dangerous things so long as they can maintain the illusion of control.
In terms of cars: Streets where built for people or animals walking on them and cars quickly started killing large numbers of people. The response was not to make cars safer by say physically limiting them to 10 MPH, but to remove people from streets.
A fairly high fraction of early aviators where killed, that did little to slow adoption of aircraft.
Astronaut deaths where sadly common, but also expected and did little to slow progress.
Umm, reasonably sure that implementing a legal speed limit was an initial response, in the UK at least. It took a number of years (and likely a lot of propaganda, though I haven't looked that closely into it and history is, of course, written by the victors) to allow motorcars to use roads at anything close to a reasonable speed.
Check wikipedia out: https://en.wikipedia.org/wiki/Speed_limit#History
Watch this and suddenly those mentioned speed limits are completely reasonable. https://www.youtube.com/watch?v=954L9MpfCEo
Note, 10MPH would allow for 2-3x the speed of a horse over long distances. So, in this alternate history cars would still have been very useful.
Thus you get jaywalking as a crime, and justified many deaths as people breaking the law instead of the naritive that cars are insanely dangerous and should be banned. In theory cars could have been banned, but in practice their advocates had little trouble changing perceptions.
If a pedestrian starts to cross the road, they have right of way. I've been on roads in some city centres where vehicles have to be very, very careful as there's a road through a pedestrianised area and people are rather bold crossing the road. If the vehicle was to cause injury, the driver would likely be liable.
No, it's literal control. They'd rather operate a vehicle in a way that's statistically less effective (where effective is defined by a collection of algorithms, we all know how perfect algorithmic generated routes are) than lose that control for a small benefit. Control itself is worth something to people.
Also, interesting fact: Subaru is achieving these impressive stats using stereo vision, not lidar.
I've felt the same way after watching various autonomous driving demos (like Tesla's[1]). But then I remember my experience of actually trying the same speech recognition software myself; under unrehearsed real-world conditions with edge cases and human mistakes, the technology performed terribly. Any "intelligence" I'd seen in the demo was essentially smoke and mirrors.
Granted, current autonomous vehicle technology incorporates a lot more artificial intelligence than those speech recognition demos ever did, but the challenge is also significantly greater (and more life-critical). Sure, your sensors and cameras might be able to read signage correctly in 99% of conditions, but when there's graffiti on the sign at night during heavy rain, all bets are off. The human driver may have difficulty also, but the human driver has real intelligence and life experience in a variety of domains, enabling them to make inferences based on more than just statistical probabilities.
In my opinion, prior to solving all the edge cases at an acceptable level using AI, we'll solve a different problem allowing us to sidestep many of those challenges; we'll incrementally start building (and converting to) smart roads where only smart vehicles are allowed. Obviously it won't be everywhere, but the most important routes will be covered, and your safety on those routes will be much higher than it would be on traditional roads with AI or human drivers.
[1] https://www.tesla.com/videos/autopilot-self-driving-hardware...
I remember talking to Apple's Kim Silverman, ¿head? of speech recognition, somewhere in the end of the '90s. He said you had to spend a few hundreds of hours training the recognizer to get at a good level. That's not a lot more than one would spend learning to touch type at speed, but a large fraction of _that_ time is productive; training a speech recognized wasn't.
Also, touch typing, once you can do it, works everywhere; speech recognition didn't work as well when there was background noise or echos. So, few people were willing to invest the time. And they probably were right.
I also agree with your statement that we will solve restricted, but useful domains first, and that a general solution for autonomous driving will be a long way of.
I also agree roads will be adapted to the self-driving cars. It isn't rocket science to embed a steel wire in the center of each car lane that a robot car can detect, for example.
I remember a television program where the engineers of some European car manufacturer thought universally usable self-driving cars would be safer than human driven ones in 10 years or so, but their human factors specialist said it would be something like 40 years before they would hit the road because she knew you can't expect humans to fully attend to driving on very short notice for a few seconds each week.
(that show also said, and showed, that features such as lane assist are more limited than the cars are capable of because of human factors)
This could be a big improvement for both safety and driving comfort and seems as if it would be a much more amenable to solving over, say, a 10 year horizon than a cross-town Manhattan taxi ride at rush hour.
In the vast majority of the cases, that sign will have been seen by another autonomous car on a sunny day before it had graffiti, and stored in the map database. You should be comparing a whole fleet of autonomous vehicles learning from each other versus an individual human.
A human will spot a person wearing headphones and recognize that person has a low situational awareness. The computer doesn't come close to even having the optical resolution to do that if the AI was perfect - remember human vision is 570+ megapixels, even a 4K video stream is literally two orders of magnitude lower.
[Now think about the fact that if we built a camera capable of recording 400 megapixels, you'd currently need to schlep around a ~750 lbs 25 node cluster, consuming about 50 horsepower to feed it with electricity, just to be able to process the video stream at 25 fps. Moore's law aint' growing that fast these days, so matching the resolution of human vision is not a realistic option.]
Another example is kids. How does the AI recognize that the 5'1" 30-year-old woman has much better awareness and can be treated differently from the 5'2" 12-year-old boy? Humans can spot that difference even from behind.
How about recognizing an adult who is drunk? Or a blind person? Mourners at a funeral, or fans celebrating after a football game? Or a million other conditions that significantly affect pedestrian situational awareness that human drivers will instantly infer from context?
What will happen when kids figure out they can stop a driverless car on its way to collect its owner just by standing in the street in front of it? They'll have a lot of fun, for sure.
How about when carjackers figure out the same? That they can dress up like construction workers, stop the car in the street, tow it onto a flatbed with built-in RF jammer and head straight for their underground chop shop? There goes your cheaper insurance.
This seems to come from http://www.clarkvision.com/articles/eye-resolution.html
But that number is a calculation of the maximum resolving power of the human eye filled across a 120 degree field of view. The fovea is the only portion of the retina that actually attains that acuity and it encompasses roughly 2 degrees in the center of the retina.
There are roughly 120 million rod cells and 6 million cone cells in the retina. The rod cells for color vision and cone cells for low light. As each individual rod cell is primarily sensitive to one of red, green or blue they match fairly well to the rgb channels of a pixel. So the eye could be considered to provide data roughly equivalent to a 40 megapixel color image and grayscale 6 megapixel. So ~5 times a 4k image.
Edit: And even that actually over estimates the amount of data the brain is actually processing. A 4k 60 fps video is handled by 6Gbps and the human optic nerve only has roughly 8.75Mbps of bandwidth.
That all people are classified as drunk children wearing headphones with low situational awareness.
The situations you describe are rare - I've once had a diplomatic event that required weird rerouting and twice had cases where traffic was regulated by hand signals due to some crash on the road, but that means just a few cases over a whole lifetime. A system that can't solve these cases but recognizes them as unsolvable is a quite acceptable automated system if it can delegate control to a human inside or a remote dispatcher, which isn't that hard to do.
And this is just me driving (i.e. my car is parked 90% of the day). If you're talking about a self-driving Uber in D.C., one of the above events will happen on a daily basis.
http://www.masslive.com/news/index.ssf/2017/05/east_longmead...
Of course, there's a very reasonable argument that e.g. level 3 automation might cause fewer accidents overall, even if it kills people when it has no idea what to do, but convincing Joe Public that such a car with such a known flaw is safe is another matter.
Not that's not sufficient.
If ten people did that in a critical area during a high demand hour it would be a news story and there would be criminal charges depending on the details.
If you redefine "sufficient" to include stopping your car on the George Washington bridge because it's confused by a construction zone it still doesn't solve the backup you cause.
One of the biggest challenges that automated systems face is that the acceptable failure rate for them is far below the acceptable failure rate for humans in the same role. To err is human...
The difficult part - when there is an error in these signals, or things shut down, autonomous cars will suffer much bigger problems than human driven cars.
Its these edge cases that are the problem. We already rely on such mechanisms for planes(information comes from both gorund control and on-flight radar). But a lot of care and resources are is required to get to $n 9's level of reliability.
Sounds costly to me. There are a lot more roads than airport runways. And then the big question is: Who is going to pay for it?
Computer speech recognition now has a greater accuracy than human speech recognition, but the types of use cases for talking to a computer are much less sensitive to error. Short snippets and phrases that are designed to get something done right now.
Compare ordering paper towels with Alexa, to asking a friend for a paper towel when your hands are messy. If your friend mishears you, they can just look over, see your dirty hands, and figure out you probably asked for a paper towel. Alexa has no such benefit, computers are held to a much higher bar.
> People thought intelligent voice-computer interfaces were just around the corner,
I would argue it isn't recognition accuracy that makes complex scenarios hard. I've seen context aware recognition being rolled out for keyboards recently (Android's keyboard does it now days, it'll correct the past word based on what the next word is), and it seems like Android does the same for speech reco, based at least on observed behavior during use, but I'm just guessing.
The real hard part is making computers smart enough to do useful things.
We are a long way off from
"Book tickets at The Altair for between 6pm and 7:30pm next Friday and add the reservation to my calendar and my wife's calendar"
being possible in all but a few contrived scenarios. (Now that said, the above scenario is getting easier and easier if you ignore voice, ML is good at figuring out emails that have schedules in them, and forwarding them to other people is now simple, everything is much better than 5 years ago!)
>Computer speech recognition now has a greater accuracy than human speech recognition, but the types of use cases for talking to a computer are much less sensitive to error. Short snippets and phrases that are designed to get something done right now.
You just said that speech recognition doesn't work in general. In general is exactly where self-driving has to work. If we just needed self-driving trains, we'd have them already*
*We do have them, but strangely there isn't much demand since human train drivers appear to do an ok job most of the time.
I replied that the accuracy is high. It turns out, in retrospect, that accuracy and usefulness are two different things.
In regards to automated driving, achieving better than human isn't all that hard. Heck backup cameras with little "warning zone" lines on them are better than human for the one particular task of backing up. Cruise control systems that maintain distance are better than humans. We are incrementally getting there. The progress is much different than with voice reco.
The problem with voice reco isn't recognition technology, that works fine, it is with having computers understand what the hell to do with the voice. Contrast that to driving, where the end goal is easy to list - Rule 1: Don't hit anything. Rule 2: Get to the destination. (Rule 1 is the hard part, Rule 2 99.9% solved!)
With Voice Reco, we got the transcription part down, but... now what? In the example I gave up above, knowing how to make a reservation is painful thanks to market fragmentation (not everything is an API), and people generally don't go and tag all of their contacts with their relationship status. I happen to have my wife under "wife" and my mother under "mother", that simple step alone gives me much more natural usage of voice input.
Then when I saw "OK Google, directions to my Mother's house", well, that still doesn't work for a thousand little reasons[1], even though each and every word was correctly transcribed. (I get a nice Google search instead!)
The set of situations that can happen while driving is far smaller than the set of interactions that can happen over voice when users expect a natural interface. Yes driving is really complicated, but it is possible to get a group together and after a day or so, brainstorm everything that could happen on the road out to 2 standard deviations of likelihood.
It might take an hour+ just to list all the ways someone might ask for directions.
[1] Mainly because no one programmed it to understand that particular way of making a request. It is annoying because I can ask it for directions to home, and that works fine, so I just figured directions to "Contact Name's House" would also work. Of course if I lived in NYC I'd expect "Contact Name's Apartment" to work!
If I type "remind me at 9am to water the plants", it does the right thing 100% of the time.
If I say "OK, Google, remind me at 9am to water the plants"...not so much.
If it just got "remind me at 9am" 100% of the time, I'd be satisfied. The fact that"water the plants" becomes "watering lamps" doesn't matter--I can figure out what I meant.
But it doesn't transcribe "remind me at 9am" correctly. It knows what to do with that text, but it doesn't get that far reliably enough.
Maybe I haven't tried saying this to humans enough for comparison, but right now, I'm not satisfied with the transcription of even the most common phrase. (Well over 90% of what I say to my phone starts with "OK, Google, remind me ..."
---
For fun, I just tried reading this out to my phone, and it got that phrase all three times:
> If I type remind me at 9 a.m. to water the plants it does the right thing 100% of time if I say OK Google remind me at 9 a.m. to water plants not so much if it just got remind me at 9 a.m. 100% of time I'd be satisfied the fact that water the plants becomes watering clamps doesn't matter I can figure out what I meant but it
Not bad. It cut off partway through, and maybe I need to speak my punctuation, but it's less error prone than normal. Helps to speak very clearly, unsurprisingly.
Hello, Apple Newton, may you rest in peace. I'm not convinced we'll have handwriting recognition within my lifetime, and if we do I imagine that shortly after I'll go looking for Sarah Connor :)
The big difference is a mistake in a car is more likely to cause injury than a misdelivered letter.
Someone is going to be the first in self driving cars. Uber has a tremendous demand for them. It would be stupid to not at least be trying to be the first one on the scene.
https://www.theguardian.com/us-news/2017/jun/17/uber-drivers...
You seemed to imply that this is a new phenomenon that isn't yet legitimized. It's been around for a long time. It was and continues to be a problem, but Uber is just a microcosm of it.
Toyota is way behind in the game. What do you expect them to say about the competition?
Do you ever wonder why there are two pilots on every commercial airliner? It's not because airlines like paying so many more pilots- notice how fast flight engineer/navigator positions disappeared as flight management technology and GPS made them unnecessary. But still two pilots are there on every commercial flight, why?
Simple answer: the airline industry has learned, through a lot of lessons in blood over decades, that even with automation you really need a pilot who is always ready to intervene right this second, not in three minutes after they've mentally caught up to what the situations is. And in order to provide that sort of guarantee over many hours, you need two pilots, so they can switch off responsibility. That's because commercial airliners on cruise, way above any animals, terrain, etc. still have situations where immediate human intervention is safety critical. (And when pilot minds fall behind the power curve the result is things like AF447, so it seems like the industry is right about the importance of this human monitoring and intervention.)
So if this well studied, easier externals problem requires someone on ready for immediate intervention at all times, how quickly do you think that a much harder problem like driving is going to get solved sufficient to allow human free driving?
This is a highly disingenious use of the word autonomous. Airplane "autopilots" are given a set of waypoints and will fly a straight line between those. That's been possible with cars since (at least) the 1960s too; today it's easy enough that you could give it as an end-of-term project for a bunch of robotics undergrads. It's also completely useless outside of very specialized situations like the mining dump trucks you mention.
It's like saying that we've had factory robotics for decades and so we should soon have useful robotic housekeepers (in the general sense, not the Roomba sense).
In stark contrast with lane-swerving cars, intersections everywhere, temporary rerouting because of roadworks &c.
Running trains must be orders of magnitude simpler than fully autonomous vehicles.
As for planes, they have a massive benefit in being engineered and maintained for levels of reliability no car can ever hope to achieve, having an awful lot of empty air around them (not to mention being able to move in the Z plane, too, to avoid collisions.
I don't doubt there are many lessons to be learned by designers of autonomous vehicles from work already put down in the fields of trains and planes - however, I'd argue they are very different problems.
And at least Siri is completely useless without a data connection.
> What people don't realize is that full autonomous driving will require more than just faster/smaller/cheaper technical innovation - it will require the refinement of innovations that probably haven't even been invented/researched yet.
Like what? Object detection/recognition? Better sensors? Path/trajectory prediction? Vehicle control? Sensors and processing/unifying their data? The hardest part is letting all these building work together, and then produce a mass-production product from it, but we do have the base technologies, companies like Google, Tesla and Volvo have proven already that.
The problem comes down to software, and Toyota has the problem that it's a hardware-focused company. In the car-industry, just like in any industry, software will become more and more important, and Toyota - just like many other car-companies - simply doesn't have an answer here since they don't understand it.
I don't think the technical aspects are as difficult for the 99.99% of the cases. It is the 0.01% of unknowns that will be difficult to overcome. But we can minimize that by modifying or building cities specifically for self-driving cars.
The most difficult part I think is the legal/regulatory issues.
This is why I see self-driving cars taking off in china/asia first before the US. They'll probably limit it to city limits initially. And when the technology is mature enough, broaden it to the entire country.
I can't help but think about speech recognition 20 years ago. Many of the hot software packages claimed something like 96% accuracy, and that sounded great on paper. People thought intelligent voice-computer interfaces were just around the corner, yet here we are in 2017, and Siri/Alexa/Cortana are barely becoming usable (but still frustratingly lacking in many situations).