http://mashable.com/2010/10/09/google-cars/
It’s a logical evolution from the ability of Google Maps/Earth to generate driving directions.
Beyond the obvious predatory lawyer issues, the challenge a Google car might create is similar to the problem created by ABS. While ABS is a good technology, a side effect is it creates more accidents – when the car following does not have ABS. The shorter stopping distance of the first car causes the following car to rearend the ABS car in an emergency stop when following at a “normal” distance, which is based on the assumption of both cars having similar reaction times and deceleration rates.
It would be interesting to know how the car makes a stop/go decision at a yellow light. Human behavior on this varies wildly, largely driven by the degree of local enforcement. If I can stop safely when a light turns yellow, I stop – it’s what I was taught. I am aware however that many people use the rule “can I get away with running the red light?”. My stopping often creates a problem. That may be what happened with the one accident they had so far.
Art points out one of the great issues with automation – decision making. Yellow lights, road conditions such as ice and snow, road construction or even incorrect directions to begin with all pose challenging situations for automated vehicles.
So, do we create automated vehicles because we can, or is there a problem to solve in doing so? I suspect this is a technology looking for a solution.
I read the article. Urban tests are one thing. I’ll be really impressed when the Google car can detect and safely avoid deer and opossums at night on winding country roads.
Excellent point – grew up in NW PA – I do miss the winters I don’t miss road animals.