Slashdot Mirror


How Autonomous Cars' Safety Features Clash With Normal Driving

An anonymous reader writes: Google's autonomous cars have a very good safety record so far — the accidents they've been involved in weren't the software's fault. But that doesn't mean the cars are blending seamlessly into traffic. A NY Times article explains how doing the safest thing sometimes means doing something entirely unexpected to real, human drivers — which itself can lead to dangerous situations. "One Google car, in a test in 2009, couldn't get through a four-way stop because its sensors kept waiting for other (human) drivers to stop completely and let it go. The human drivers kept inching forward, looking for the advantage — paralyzing Google's robot." There are also situations in which the software's behavior may be so incomprehensible to human passengers that they end up turning it off. "In one maneuver, it swerved sharply in a residential neighborhood to avoid a car that was poorly parked, so much so that the Google sensors couldn't tell if it might pull into traffic."

10 of 451 comments (clear)

  1. Very pokey and slow by Anonymous Coward · · Score: 2, Interesting

    From what I have read from people who have actually interacted with a autonomous car. They are very pokey, slow, and tend to pause trying to figure out what to do.
    In fact many times its the required human driver who has to intervene in order to help the car out of a jam. I think the more we try and mix these auto driven vehicles with human one's the more we will experience the growing pains of this technology.

  2. culture dependent by Chrisq · · Score: 4, Interesting

    “They have to learn to be aggressive in the right amount, and the right amount depends on the culture.”

    Very true, When holidaying in Texas I quickly found out that stopping for a red light that had just turned would upset drivers behind me. The lights had a much longer amber time, so a whole lot of people who would have had to brake for the lights in the UK would go through

    1. Re:culture dependent by Pentium100 · · Score: 4, Interesting

      Depends on the location. In my country, a yellow light means you can legally drive out of an intersection (for example, if you are turning left), but not into it, unless you need to brake suddenly, in which case you can go.

      Now, "brake suddenly" is a subjective thing. If I see the light some distance away and do not need to slam on the brakes to stop, then I stop. It may cause an inattentive driver to hit me from behind (happened recently when I stopped to allow a pedestrian to cross as required by law).

      However, it is also the law to leave a safe distance between you and the car in front so you can stop without hitting it if the car in front of you suddenly stops. If you hit another car from behing, you will almost always be found guilty (pretty much the only hope for you is for the other driver to be drunk - drunk drivers are always guilty for an accident even if they did not cause it - this is done to discourage people from driving drunk).

  3. Re:In other news by Anonymous Coward · · Score: 2, Interesting

    Millions of people on the road today deserve to have their license taken from them because they can't follow simple rules like signaling, not parking halfway out into the street and leaving enough room to brake in case the car in front of you brakes.

    Due to this - I am a pedestrian - I'd much rather have self-driving cars.

  4. Programmed behaviour is programmed behaviour. by ledow · · Score: 5, Interesting

    If the programming makes it jerk the steering away from a stationary hazard rather than, say, detect it earlier and slow down as it approaches, then it's not suitably programmed for coexistence with unexpected stationary hazards (Not even anything to do with human presence! What if that was a cardboard box and it swerved heavily in case that box "pulled out"?).

    If it can't make it's way through a junction where the drivers are following the rules, that's bad programming. If it can't make it's way through a junction where other drivers don't come to a complete halt for it, it's not fit to be on the road with other drivers.

    If you want a car to co-exist on the road, it has to be treated as a learner driver. If a learner driver swerved at a non-hazard, they would fail. If a learner driver refused to make progress at a junction because the masses didn't open up before it, they would fail. So should an automated car.

    Unless - and this is important - you are saying that automated cars should only operate on automated roads where such hazards should never be possible and they are deliberately NOT programmed to take account of such things. Which, in itself, is expensive (separate roads with separate rules with no human drivers), stupid (that's otherwise known as a "train line", and because they can't do anything about it it will hurt more when it does happen), and dangerous (because what happens if a cardboard box blows over the automated road? etc.).

    Program to take account of these things, or don't plan on driving on the road. The safety record is exemplary but equally there are only a handful of them and the eyes of the world are on them, and there are still humans behind the wheel, and even by miles travelled each one is probably dwarved by a single long-distance driver over the course of a year - and it's not hard to find a long-distance driver who's not had an accident for years.

    If you're going to be on the roads, then you need to be able to take account of all these things, the same as any learner driver. Sure, you didn't hurt anyone by swerving or not pulling out, but equally - in the wording of my first driving test failure - you have "failed to make adequate progress" while driving.

    A car sitting on a driveway would have an even better safety record but, in real life, it's still bog-useless compared to a human. Similarly for any automated vehicle that just stops at a junction because it can't pull out, or swerves out of the way of a non-hazard (and potentially weighs up collision with non-hazard vs collision with small child and gets it wrong).

    1. Re:Programmed behaviour is programmed behaviour. by Cassini2 · · Score: 5, Interesting

      If it can't make it's way through a junction where the drivers are following the rules, that's bad programming. If it can't make it's way through a junction where other drivers don't come to a complete halt for it, it's not fit to be on the road with other drivers.

      The problem is that people don't follow rules. We follow approximations of the rules. For instance, my driver's handbook described the correct way to deal with yielding at a four-way stop as "yield to the person on the right." For a computer, that's an obvious deadlock situation, or worse - an obvious mistake. If four cars are parked at a four way stop, and each car yields to the car on the right, then (a) a situation could occur where no one goes anywhere, and (b) if the individual cars only pay attention to the person on the right, then they could hit an on-coming car turning left, or the car on the left turning left. People process the "yield to the person on the right" rule into something much more complex.

      People use a number of complex behaviours at four-way stops. Firstly, the wave of the hand, or the nod of the head to indicate that you yield to the other driver is an important signal. Secondly, in my jurisdiction, 90% of the four way stops are done on a first-come first-served basis. Lastly, and this is the bit I don't understand, often people yield to the person on the left. The actual system of navigating a four-way stop is much more complex than what an initial computer implementation might be.

    2. Re:Programmed behaviour is programmed behaviour. by edtice1559 · · Score: 4, Interesting

      You can't program the self-driving car to break the rules as it opens up all kinds of moral and (more importantly, or at least more expensively) legal liability issues. You have a human driver for that situation until the proportion of self-driving cars increases enough to change traffic characteristics.

  5. Re:Poor example by wstrucke · · Score: 4, Interesting

    "One Google car, in a test in 2009,..."

    One would think that in 6 years some improvements would have been made. Do we have a more current example?

    It mentions further down in the article that that particular example has already been corrected.

    ... For instance, at four-way stops, the program lets the car inch forward, as the rest of us might, asserting its turn while looking for signs that it is being allowed to go.

  6. Re:Poor example by Braedley · · Score: 5, Interesting

    As it turns out, we do. A Google Self Driving Car and a cyclist on a fixed gear bike met at a 4-way stop. The cyclist was doing a track stand (staying upright on the peddles, sometimes peddling backwards and forwards a small ammount) instead of balancing on a foot. This caused the Google car to think the cyclist was going to enter the intersection after the car had started moving, causing it to stop and "wait" for the cyclist, which by this point had "stopped", which the car took to mean that he (the cyclist) was waiting for the car to go (which was actually the case), and so the car would start moving again until the cyclist started his next forward motion to balance himself.

  7. Re:Poor example by jbengt · · Score: 4, Interesting

    It's like being on a escalator at the airport or train station. Two folks don't know where they are going. So they stop dead in their tracks at the end of the escalator, blocking the path for all the other folks on the escalator.

    That is a well known problem in architectural design. Give a clear path for people to exit and clear escalators and the like, and place directional signs where people have space to stop to read them. There's an art to finding a way to entice people away from stairs and escalators after they exit them.