ANOTHER OF Google's self-driving cars has been involved in crash, although this time the fault most definitely lies with the other, very human, driver.
A report fresh off the presses from the State of California’s Department of Motor Vehicles (DMV) explained that a Google self-driving car was minding its own business at the intersection of Cuesta Drive and Springer Road. That’s in Los Altos, for geography fans.
Then, out of nowhere, a human idiot came barrelling down the road at a shocking seven miles an hour and rear-ended the defenceless Google car.
“The Google AV [autonomous vehicle] sustained minor damage to its rear hatch and sensor,” the DMV report said.
Google added that the company was unable to determine whether the other vehicle sustained any damage because “the driver left the scene without exchanging information”.
'Brad, you just hit one of the Google self-driving cars?!'
'Oh man, my dad is going to kill me! I'm outta here!'
Don’t worry, though, California’s finest, i.e. the police, are on the case having been “notified of the incident”.
The accident is the latest involving one of Google’s cars, but is perhaps not as notable as some of the others, the most prominent of which saw one of its cars career into a bus because it got confused.
Nevertheless, the story raises some interesting points, not least that such a slow impact speed still managed to cause damaged to the rear sensor.
If we do all own self-driving cars in the future, are we constantly going to have to get new sensors fitted every time they get nudged and pranged? If so, how much is that going to cost? We can’t imagine it will be cheap.
'Yeah, mate, your rear sensor thingamajig has gone. You're looking at, ooh, £150,000 to replace that.' µ
Though it's not exactly an even playing field
Biz machines offer of Intel CPUs and AMD or Nvidia graphics
Thermal throttling is hampering the overclockable chip's performance
Firm is making its Lightning port even more locked down