Will the Google Car Turn Out To Be the Apple Newton of Automobiles?
An anonymous reader writes The better question may be whether it will ever be ready for the road at all? The car has fewer capabilities than most people seem to be aware of. The notion that it will be widely available any time soon is a stretch. From the article: "Noting that the Google car might not be able to handle an unmapped traffic light might sound like a cynical game of 'gotcha.' But MIT roboticist John Leonard says it goes to the heart of why the Google car project is so daunting. 'While the probability of a single driver encountering a newly installed traffic light is very low, the probability of at least one driver encountering one on a given day is very high,' Leonard says. The list of these 'rare' events is practically endless, said Leonard, who does not expect a full self-driving car in his lifetime (he’s 49)."
didnt RTFA but seriously? Google car can't recognize a red light??
I would've thought some of the better Slashdotters could write software that recognizes a traffic light from a camera feed, let alone the geniuses at Google.
Perhaps more of a concern is the issue where the car will fail in rain/snow, both of things people in the Bay Area rarely experience.
If they built special lanes or only worked on places like the Freeway. It would be nice to have a self driving car for a 6 hour road trip and then manually take over in the cities or where the car had issues.
Visit the Arcade Restoration Workshop @ http://www.arcaderestoration.com
"said Leonard, who does not expect a full self-driving car in his lifetime (heâ(TM)s 49)."
He is a man of limited vision. I did a lot of AI research and development, long ago, back in the dark ages of computing, and I disagree. I'm only a few years older and I do expect to see fully self-driving cars in my lifetime. Perhaps I merely will live longer...
Beat up Martin.
Eat up Martha.
http://i.imgur.com/06fu9sE.jpg
Unless my history is rusty, Newton begat the ARM chip that we all know so well.
W..w..W - Willy Waterloo washes Warren Wiggins who is washing Waldo Woo.
The first vehicle with this technology is not going to be a personal car, or anything that resembles a personal car (like a taxi). It's going to be semi trucks with trailers.
From a conference I sat in on last week (dealing with railroads, not trucks themselves), the turnover rate for truck drivers is over 100% per year. This is considered a plus for the railroads. I say that this is a plus for autonomous trucks. They drive autonomously site to site, and then, a driver takes over to get them parked into the loading dock (most likely), the trucks manage to do this autonomously (maybe, but not the scenario I see winning out, not at the beginning), or the docks are redesigned to make it easy for the autonomous trucks to park them in loading position (what will happen once autonomous trucks are widely used).
Yes, I realize other changes will have to be made. Refueling will have to be done manually in the beginning. That may mean the truck stop hires a person or two, that then takes care of the autonomous trucks, and I'm sure the owners will gladly pay a bit of a premium to get their trucks fueled. At least until the automated fuel pumps for the trucks are in place, at existing or new truck stops.
I have zero doubt that my great grandchildren won't have to learn how to drive a vehicle. I have grandchildren, and yes, I expect that they will have to learn how to drive, the technology is moving that fast.
Yet.
Bryan
Humans have rules for driving. For example:
-> If you see a traffic light, identify what color it is, then continue, slow down, or stop based on one of those 3 colors.
So the Google Car cannot identify a traffic light? Or if it does, it cannot identify its color? If so, is that a weakness in the computing power? Like, a supercomputer could do these things, but a reasonably sized onboard computer cannot? Or a weakness in "vision" sensors?
-> Paper versus rock in the road: This, I can understand. There are a myriad things in the road. The decision here is, can the car safely pass over it? Inability to determine this is due to vision sensors or limitations in computing power?
I saw an interesting problem the other day: a piece of wood baseboard trim (for a wall) blew off a truck. It seemingly hung suspended in air then came down. I hit my brakes but kept going straight, hoping for the best. It hit the ground, bounced and lay flat. I imagine that might legitimately freak out an autonomous car.
A moron can drive safely, through city traffic, if he's highly motivated, manages to keep his attention on the road and his speed down. I guess a moron is still more capable of navigating the world than a computer.
almost genius in its idiocy. If self-driving cars really start to hit the roads, cities would definitely mandate that all traffic lights show up in maps, and require that traffic lights show up in maps before being installed. This is not a problem of the driving car, it's a problem of trying to imagine future technology in a current context, which is of course always going to lead you astray.
Plus, as other commenters have said, self-driving cars can definitely recognize traffic lights. It's just that right now they aren't quite as good at doing that as humans are. The reason is that traffic lights and construction cones and stuff like that are optimized for human visibility, not robot visibility. It's quite trivial to adapt them for robot visibility as well (perhaps even incorporating stuff like specialized radio signals).
I predict that horseless carriages will never take off because without an animal like a horse with hooves on the ground, you could hit rocks and fall into ditches without knowing it.
A fool and his hard drive are soon parted.
It really depends on how much "safer" autonomous cars are doesn't it. The current problem with software is that when it fails it fails usually catastrophically, what do you do when you fail, stop that could be dangerous, keep going dangerous too. People don't usually fail as completely as software they make lots of small mistakes but usually do a good enough job.
the road toll is 14.9 per 100,000 per year that is quite low considering how much people drive, you would need a lot of testing, in real life scenarios to convince me that automated car was safer. And each release would need that level of testing. Yes you may get one driver who is bad kill a few people but a bad software release could kill much more.
I am not saying automated cars aren't safer, just that just because they are automated doesn't automatically make them so.
The Google car doesn’t know much about parking: It can’t currently find a space in a supermarket lot or multilevel garage.
It can't consistently handle coned-off road construction sites, and
its video cameras can sometimes be blinded by the sun when trying to detect the color of a traffic signal.
Because it can't tell the difference between a big rock and a crumbled-up piece of newspaper, it will try to drive around both if it encounters either sitting in the middle of the road.
Use a little imagination and you can surely think of other issues.
"First they came for the slanderers and i said nothing."
The only way a car can be designed to safely self-drive is doing it just the way we do: by creating a local, up-to-date mapping of the surrounding area in real time and working within that representation with sufficient skill to respond to anything that might appear.
Pre-existing environmental mapping simply cannot keep up. Construction, pets crossing the road, wild animals, falling rocks, pedestrians, vandalism of road signs and traffic indicators and lane painting, washouts, drunks, heart attacks, stinging insects, oversize loads swinging around traffic lights and signs, special transports, some guy at the side of the road madly waving a hand-printed sign that says "BRIDGE IS OUT!"... the list of unpredictable effects upon the local driving environment seems almost endless -- and keep in mind these things can occur in combinations of more than one type and more than one incident. Often suddenly.
Further, if the car is smart enough to be capable of updating the environmental map in real time and deal with any combination of changes, then it's already smart enough to maintain a completely dynamic local mapping and doesn't need a pre-existing mapping for anything but gross navigational purposes (route planning) and even that can require the vehicle to adapt.
Contrariwise, if it isn't smart enough to maintain a full local environmental mapping, then it is inherently unsafe.
Someone(s) at Google didn't think this one through.
I've fallen off your lawn, and I can't get up.
The expectation of this article is that Google will somehow shortly produce a car which will completely replace drivers in all circumstances. Clearly, that's the eventual goal, but that's not needed to produce something useful. Car companies are already churning out various incomplete solutions that help with highway driving or parking.
I expect their initial product to be something that works as a taxi in semi-controlled circumstances, or something that makes driving more convenient, but which requires intervention some of the time. Either of which would be a viable product.
Early cell phones were overpriced bricks, but they were still useful to some people. It took a huge investment from many companies and quite a bit of time to get to the point where people considered dropping their land lines. Replacing the old generation of technology is not usually a sudden process, but involves a lot of gradual improvement.
My motto is "Find a fucking dictionary"
You're welcome
Sounds good! Newton was commercially available, has a loyal fan base and inspired successive generations of more polished and popular products, including Palm and Apple's own iPhone. True, there is no guarantee that just because you release an early adopter product, you will reap most of the benefits when technology matures. But not being on a lookout for new things guarantees slide into irrelevance, like Kodak or Borders. Besides someone got to do it.