Google Self-Driving Car Might Have Caused First Crash In Autonomous Mode (roboticstrends.com)
An anonymous reader writes: While driving in autonomous mode, a Google self-driving car was involved in an accident with a public bus in California on Valentine's Day, according to an accident report filed with the California DMV.The accident report, signed by Chris Urmson, says the Google self-driving car was trying to get around some sandbags on a street when its left front struck the bus' right side. The car was going 2 mph, while the bus was going 15 mph.Google said its car's safety driver thought the bus would yield. No injuries were reported. If it's determined the Google self-driving car was at fault, it would be the first time one of its cars caused an accident while in autonomous mode.
Not might. It did.
Trying to build a car that can drive itself and cover all cases is too hard. You need to start small and slowly add more and more safety features to a vehicle before it can handle most of the difficult scenarios of accidents.
Ow my neck!!
SJW's don't eliminate discrimination. They just expropriate it for themselves.
>> Google said its car's safety driver thought the bus would yield.
So Google is teaching their cars to drive like normal Californians: expect that the other guy will yield.
in some jurisdictions, cars have to yield right of way to buses in general.
Buses certainly have right of weight.
Also, what's with the aggressive / obnoxious sneaking around cars in same lane tactic. Did someone program that or did the software learn it?
Where are we going and why are we in a handbasket?
Just stay out of the way, problem solved
“He’s not deformed, he’s just drunk!”
I'm a big believer in autonomous cars, but when I see
Google said its car's safety driver thought the bus would yield.
it makes me wonder how many crashes we would have had in autonomous mode, if there weren't an attentive driver who was fully aware he was sitting in an experimental vehicle.
Even if the first rounds of autonomous cars still require a driver for override (for legal reasons if nothing else), it seems like the number of autonomous crashes that likely would have happened is the number has to be driven way down to be comparable to, or less than, the ones with human drivers*; it's not really the amount of autonomous crashes overall that is important.
Also makes me wonder whether any of the manual mode crashes were initiated in autonomous mode and the manual override driver just couldn't recover the situation.
*whether average human drivers or above-average human drivers or even below-average human drivers are the standard is up for debate.
I know I can.
No jury would find against the human and in favor of the robot.
-- Tigger warning: This post may contain tiggers! --
Neither school buses nor soccer moms ever yield in traffic.
That car must be drunk
1st rule of defensive driving- never expect another driver to do anything
I won't yield into traffic or turn into a street if another driver will need to slow or brake not to hit me
Never sit in a median to turn with front or back of car sticking out
I actually speed up a bit before turning to maximize distance between myself and driver behind and turn shallow. This is a bit hard to explain but you angle into the turn and actually do most of your slowing when you are already in the turn
Many others but I probably don't even think about them.
love is just extroverted narcissism
On my news feed, a couple lines below it I have the following headline:
Jalopnik Idiot Street Racers Blamed For Massive Freeway Wreck That Killed Three.
I can't wait to see google cars drag racing.
Could somebody please come up with a fitting car analogy?
love is just extroverted narcissism
Google is now saying they were following the "spirit of the road" when the crash happened and that they've reviewed the incident, as well as thousands of variations on it, in a driving simulator and made refinements to its AV software.
Maybe Google should send the car with Cheech and Chong!
Ha ha
Newton's Right of Way Law: the biggest one has the right of way. In most large cities, that supersedes the Vehicle Code. Buses have the right of way if they want it. Taxis take the right of way. Uber ignores the right of way (stop in front of you without warning to pick up a passenger?). Prii and smaller (alias road boulder) must grant r/w to anything else that wants it.
This is just like when you have a self driving car that is trying to avoid sandbags and hits a bus instead.
So based on numerous descriptions I have read, the Google car was in a very wide lane and moved to the right side of the lane to make a right turn. It saw some sandbags blocking the very right side of the lane, so it tried to move back to the middle of the lane. A bus, coming up from behind in the same lane, did not yield to to the Google car and there was contact.
I think it is important to note that all of this happened in the same "lane".
While the Google car could have possibly avoided the accident, I am not sure it is to blame. It seems to me that the bus was attempting to pass a car ahead of it in the same lane.
The blame seems about 80% on the city for not properly marking the lanes, about 15% on the bus for not yielding to a car ahead of it in its own lane, and about 5% on the Google car for not stopping for the bus who was trying to barge its way through.
- (c) 2018 Hank Zimmerman
The accident was because the car saw sandbags on the right and in an overabundance of caution decided to move a whole lane over, into a bus.
Well that's as good as many human drivers who I have seen swerve from the lane they are in at seemingly nothing without a glance, and absolutely why you do not linger in someones blind spot.
An open question though is how it saw sandbags and not a BUS...
"There is more worth loving than we have strength to love." - Brian Jay Stanley
The "safety driver" has just been overriding all other would-be accidents.
Google said its car's safety driver thought the bus would yield.
BWAHAHAHAHA!!! Has this guy ever driven in SF before? A bus YIELDING to another car? In your dreams. I drove through SF for years, and buses didn't give a crap who was around them. When they pulled off to pick-up/drop-off passengers, they would intentionally park at an angle to keep the lane blocked so they could more easily start back into the lane. Even if they didn't block the lane, if they wanted to get moving in that lane, they just go. They know that they are bigger than the cars, so they know the car will slow down or move out of the way. If a lane became more narrow than they liked due to parked cars on the side of the road, they would just take up two lanes. If you are next to it in the lane that they now want to occupy? You better move the fuck over. They would run red lights at will. Watch out if you are trying to cross at an intersection with a traffic light and a bus is coming through. Without a doubt, bus drivers in SF were the worst.
The law says a right-hand turn shall be made as close as practicable to the right-hand curb or edge of the roadway. So Google's self-driving cars have been making their right turns illegally until just recently.
I expected better from Google.
Any sufficiently unpopular but cohesive argument is indistinguishable from trolling.
When they find who the bus driver was, they will be blocked from Google search for not yielding to the Google car.
Agreed, reading the report it is very obvious the bus actually caused the accident by trying an inappropriate overtake the Lexus
The Lexus only 'Caused' the accident only in so much as it did not avoid it.
...so that resources can be put to better use in driving assistance, rather than autonomous driving, which is a dangerous nonsense. Real life situations are far too complex for algorithms to evaluate and react to, on tiny roads full of obstacles and uncontrollable events.
The only way to fully automate cars would be to have separate roads, with predetermined paths either physically determined or via f.e. radio signals, adapting technology and experience from air travel like cruising autopilot and ILS.
Forcing autonomous vehicles to adapt to an analogue path instead of creating a digital path for the vehicles to follow is just approaching the problem from a hopeless angle.
The bus has the right of way. Google's car should have yielded, plain and simple.
Our car had no accidents in autonomous mode because it'll be yanked into manual mode if the safety driver percieves danger.
...is whether or not it was possible to drive over the sandbags.
Probably looks like someone forgot to set their parking break.
Where do you draw the line?
Typically, it is drawn between the lanes...
That's proprietary info, you are not going to have access to it until after a couple of gigantic court cases involving dead children.
Or one court case involving a gigantic dead child?
How can you possibly determine that someone willfully failed to avoid the accident?
When one side says "Google said its car's safety driver thought the bus would yield." When a driver sees a potential accident coming the proper response is not to bet the other guy will yield, even if you have the right of way. Sometimes you have to accommodate the other guys illegal move.
In this case; having read the article (I know, I know...) it seems that the car programming is overly optimistic about predicting the behaviour of vehicles overtaking it. It seems possible that the programming includes implicit assumptions of the likely stopping distance and reaction times it should expect from other vehicles as well. In other words; it "thought" it had sufficient space and time to perform the manoeuvre because it "assumed" a bus would behave and react the way a car might.
I have two thoughts, each in defence of one of the vehicles in this collision:
1) Even the safety driver expected the bus to yield and from I can glean from the article, legally the bus should have yielded. So this was a mistake that even the majority of human drivers might have made in the same situation.
2) Others in this thread have posted criticisms of bus drivers in their city or in general. Much of the annoying behaviours they mention though are pretty understandable from the bus drivers POV. You can't just suddenly hit the brakes if a smaller vehicle or pedestrian darts in front of you. Not only do you have a hell of a lot of momentum (highly variable, depending on passenger load) you also have to make as gradual velocity changes as you can. Your passengers aren't buckled up, you might have a fair number of them standing, with any number of knapsacks, briefcases, skateboards etc etc that become flying hazards when you come stop too suddenly. You have to ease to the left a fair bit when making a right turn because you have a much larger turning radius than most other vehicles. You have to drive straddling lines sometimes because if you stayed tight to the right, you are going to crunch someone, hop the curb or both. On the other hand, if you do stick to the left as much as you can, lots of people are going to pull what Torontonians call a "cabby pass" where the cab illegally passes a bus or streetcar on the right so as to get out from behind it. If they don't use their rear end to block the traffic lane, quite often they'll never get back out because no one wants to stop at the buses back corner and let the bus back in. (I have a relative who is a TTC bus driver and he has passed along some training and daily work anecdotes)
I need a wheelchair van for my son. Help me get the word out. https://www.gofundme.com/wheelchair-van-for-jj
Not of robotics, but driving.
I grew up and learned to drive in SF and Rule 1 was always: "Don't mess with MUNI." The quality of their drivers, the driver's attitude ("I get to go home the rest of the day if I hit something?"), as well as the law of gross tonnage made it wise to give them as wide a berth as possible.
Corollary "A" to this rule is "Never expect MUNI to do the sane thing." I would have expected this rule to have been as ingrained in Google's driverless cars as strongly as the first law of robotics was ingrained in Asimov's robots, but I guess not.
Love technology. Keep hearing people comparing how elevators were once manual now automated.
But Cars are weapons in hands of unpreditables. Too many variables for software to catch up.
I think a 98% reduction in accident rates is pretty easily doable by first-generation autonomous cars. But you know there are some people who don't think in those terms. "Look," they'll say, "here's one that drove into a bus; we mustn't let these things on the road!"
So what is needed to keep this lifesaving technology from being derailed is a concerted effort to educate people that the perfect must not become the enemy of the extraordinarily good.
That that is is that that that that is not is not.
Thanks for the street view and concise list! But that double-wide does not look like two lanes, it is a lane and a shoulder for parking. Our city does this too, and people do use it like the Google car intended to but it is not marked for turning. Practically speaking you have to consider the shoulder area near the intersection as a no-mans-land.
According to the report, they were side-by-side in the same, double-wide lane, hence the shared responsibility. Here's a Street View picture of the turn in question [google.com]. Apparently, the sequence was:
1) Red light.
2) Google car signals for a right turn.
3) Google car gets into right side of the double-wide lane and passes cars that are stopped for the red light.
My take is, even though it intended to turn right, the Google car was in the wrong to drift to the right away from the dashed white line it was obviously following on its left side. It was interpreting the space to the right as driveable. For it to be a driveable lane there would have to be either a dashed line to the right that Google car would cross over, OR a right arrow painted on the road ahead indicating it was indeed a lane dedicated to right turns. These things were not there. Google should have stayed in the lane, not have interpreted the right side as a valid to drive at all --- unless it was pulling over to stop or parking. Google car was in the wrong for passing cars to the left of it. It was driving on the 'shoulder', not within its own white-marked lane or designated right turn lane.
4) Google car has to stop because there are sandbags blocking the storm drain.
5) Light turns green, cars start moving.
6) Google car waits for cars to pass to create an opening, then slowly moves back towards the center of the lane.
Google car is in the wrong again because it was stopped and is now moving slowly on the 'shoulder' and is NOT signalling left to indicate it wishes to re-enter the lane.
7) Bus decides not to yield to the Google car that's ahead of it in the lane, trying to pass it anyway.
Google car was probably in 2mph 'crawl mode' which is not human to do at all. Humans either wait or gas 'n go. From the bus driver's relative speed the Google car probably looked like it was stopped. The Google car may even still be signalling right at this point. The bus does not see the sandbags, all it sees is a car on the shoulder.
8) Bus gets its nose a bit ahead of the Google car.
9) Google car doesn't turn the wheel back in time and scrapes the side of the bus.
Google car completely at fault. It was on the 'shoulder' not in the lane. Vehicles ahead of you lose their right of way when they leave the lane. Google car (likely) NOT signaling left to indicate re-entering the lane (because it thought was in a separate and valid lane: wrong). But even if you are signaling left to indicate you wish to enter a lane, you do not gain right of way.
So unless it was exceeding the speed limit the bus is in the right, There is the other thing, that contact was made after the front of the bus passed, which alleviates any suspicion that the bus hit something directly in its path. Google in the wrong, and they need to review the criteria for drivable lanes. If the road has clearly visible lines to your left and there are none to your right, that's NOT a drivable lane over there. Stay in your lane-position, don't pass anyone and (of course) watch your right-rear for dipshits driving on the shoulder.
Something like this happened to me. I'm centered in a marked right turn lane at a solid-circular red light. Cars on the opposite side of the intersection had all turned left and passed in front of me and now no one is coming. It is now clear for me to ta
<blink>down the rabbit hole</blink>
I expected better from Google
Why? These are still experimental vehicles, it does not make sense that they would be fully competent at all intricacies of both practical driving and legal driving (as these are not the same things, with moderate overlap) at the experimental stage.
Sticking to the middle of the lane and having "annoyed traffic" stack up behind you is not a terrible state of affairs during this stage, and it better than attempting to have the vehicle stick to the curb when the AI is not ready for it and potentially causing an accident involving pedestrians.
It never had to take a driving test like you did.
It will come defended by one of he largest companies the world has ever seen.
It will put thousands of people out of a job.
It's not likely to see a woman in woman in a black fur coat.
I can't decide whether a child or an adult dies.
It can't see at 400hz like your eyes can.
[Yes, we have persistence of about 16-24 hz, like you though you did, but we can see a new object enter the scene at about 400hz. Try it with an Aduino if you don't believe me. You can plainly see the difference between 60-120hz in monitors.]
https://www.youtube.com/c/BrendaEM
So based on numerous descriptions I have read, the Google car was in a very wide lane and moved to the right side of the lane to make a right turn. It saw some sandbags blocking the very right side of the lane, so it tried to move back to the middle of the lane.
I don't think there is any such thing as a wide lane where cars are allowed to go side by side. Whether it is marked as such by paint on the road or not the google car had moved into a right turn lane. It is common for parking spots and bike lanes and such to turn into a right turn lane near a corner. So marked with paint or not, the google car seems to have being trying to move from a right turn lane to a traffic lane. Perhaps the lack of paint contributed to the error, the software failed to recognize the right turn lane. An implicit lane even with the lack of paint on the road.
I don't think so, those things are pretty big generally. I don't know many drivers that would go over them even in an SUV.... but certainly not in a tiny car.
"There is more worth loving than we have strength to love." - Brian Jay Stanley
All the lead-up to the real problem is just noise. Here's the real take-away:
The google car had a sudden obstacle come up. It was only moving two miles an hour, and yet it did not get out of the way fast enough. Its reflexes were too slow.
This is PRECISELY what autonomous vehicles should be able to do massively better than humans.
Probably Moore's law will solve this in a few years, but we need them to be much faster than humans now, because this is how we keep people running out from between cars from getting killed by autonomous cars going faster than 2 miles an hour. We can't let them on the roads in numbers and on their own without this. One death and it's no autonomous cars for an extra decade. So Google needs to figure out how to make its collision avoidance stuff faster.
It's a huge problem, it's their problem, and they have to fix it now.
It was previously not practical to write the code to enable the feature, because they were still working out bugs in the not-riding-up-the-curb-and-hitting-pedestrians code. When that code was tested, it was practical to add new features.
I just made that up, but with a law poorly written so as to include an "as close as practical" clause, it's good enough.
It doesn't hurt to be nice.
I found it interesting that the California DMV has a checkbox for autonomous mode or conventional mode in their traffic accident form.
It should be kept in mind that if both vehicles were autonomous, they could have automatically negotiated what to do before either moved an inch, and this type of incident would never happen.
They also need to note that trains *NEVER* yield.
And I'm thinking, angled approach it's going to be difficult to distinguish a bus from a train.
Bus drivers yield to no man. Why would they yield to a machine?
I expected better from Google.
Why? Most things Google do are utter crap. One or two decent products among hundreds of duds...
Buses yielding???!?! HAHAHAHAHAHA.... ow my sides.. Buses from where I'm from never yield to anybody or anything.
Get back to us when these cars have even a 10% reduction in accident rates, can drive on roads they haven't seen before, and operate in snow or heavy rain. Until then, kindly keep imaginary statistics in the orifice you pulled that 98% from.
This is why I don't drive in the city.. there's always someone going 2 or 15 or 35 - and a blind spot, and a delivery truck or some other such crap double parked at the end of my lane. It's a lot easier to just take the light rail and read Slashdot instead.
Sorry, ABS has scarcely any effect on stopping distances, particularly in the dry, for cars. It does do a reasonable job of cycling around the peak braking friction of the tire, but compared with a moderately skilled driver (which is the problem) the difference in stopping distance is small. ABS is designed to permit you to steer and brake simultaneously, and also as a by product it handles split mu.
In the dry, even if you lock all four wheels, your stopping distance is around 120% of the best that can be achieved, and even better, you'll stop in a straight line. That's why your first instinct, to stomp on the brakes, wasn't such a bad idea, even before ABS.
For me, it's not a stretch to imagine the bus driver simply saw the name "Google" on the car, and decided to collide on purpose. If he feels sure he can prove he's "in the right," why not go ahead and do it? If without monetary gain, he may be getting satisfaction out of causing trouble for "those rich, techie a-holes"...
In the day in downtown seattle, a million big buses lined the downtown curbs, filling up who blocks of curb solid. If one pulls out in front of you and you hit it, guess who got cited. So, a special case ordinance. We might end up with a lot of those with self-driving cars.
I'm just curious. If it had been a serious wreck, and the autonomous car was at fault, whom is liable for the damages? Google? Or BMW, or Ford, when they bring autonomous cars out?
A Bus is going 15mph, next to a car from Google, the Google car is going 2mph. Something does not add up.
Why not just change the program so the Google car doesn't sneak past cars using the parking lane, and instead wait for a proper right turn at the intersection? Is there some expectation for people to pull to the parking are to make a right turn? That seems odd to me. But I'm not from an area that has a lot of on-street parking. Either it was one lane, and Google was wrong to make a second right turn lane. Or it was two lanes, and Google was wrong to veer into the other lane. I'd like to root for Google here, but I just can't figure out how it wouldn't be their fault. I'm glad they owned up and already fixed the software.