Why Tesla's autopilot can't see a stopped firetruck
wired.com
wired.com
While their technical reasoning is fine... this statement shows a complete failure of reasoning about human beings and UX. In essence they are asking people to stay alert without being active, this is actually really fucking hard to do as a human being. Noticing an object that needs to be avoided while you are already actively engaged in driving is easy, you are naturally alert and there is no "intervention time" because there is nothing to intervene with. Trying to achieve the same level of response while letting a machine drive kind of defeats the purpose of letting the machine drive.
Yes I'm basically making the argument that semi-autonomous driving is not safe. Make it fully autonomous or not at all. Two modes, keep it simple, because human concentration is complex.
Yeah that definitely sounds 100% autonomous... ship it!
I still see people driving around while holding phones to their ears. There needs to be a change to make it socially unacceptable to do this. You only need to be caught twice to lose your license.
It's also illegal to drive distracted. While it's technically legal to use a hands-free telephone, if you could be described as "distracted" because of it, it's illegal.
The autopilot is fully capable of landing the plane entirely automatically (once you tell it to, and if you're approaching an ILS autoland runway), but often times that's reserved for extremely poor weather or such, and pilots will land manually. They'll still tune the ILS so they have their localiser and glideslope information on their flight display, but they'll follow that manually rather than telling the autopilot to. This varies by airline.
On Boeing airliners there's also the (delivery) option for a pilot awareness monitor. If you don't make any inputs (change from weather to terrain radar or vice versa, change the range of information displayed on your navigation display, toggle whether airports or VORs are displayed, etc) for a short period of time (I believe it's 10 minutes), it will generate an EICAS warning.
This is attention-grabbing yellow text on a screen that the pilots are supposed to be monitoring. If you don't action that (by hitting the warning reset switch or making any input) you get a very loud very red alarm.
A big ship will have BNWAS, which is supposed to alert everybody else in crew quarters (e.g. officers asleep) if the officer on the bridge (who should be actively controlling it) doesn't do anything for a prolonged period and doesn't respond to a local warning alarm.
When there's an accident investigation with suspicious circumstances like a collision in an otherwise empty region in the middle of a calm dark night, almost invariably either the BNWAS was "mistakenly" switched off, or its mandatory logging was "mistakenly" erased or turns out never to have been enabled at all. Why? Because the alarm is annoying and there's no acceptance by owners, masters or crews that it's keeping them alive and so they must use it, so they switch it off, muffle the alarms or otherwise disable it and then, inevitably, someone falls asleep and an accident happens.
Similar tech in private cars would, I think we have to assume, end up just like BNWAS on big freighters, disabled because it was annoying. Sometimes nobody would survive the accident to cover up the fact it was disabled, but that's cold comfort.
Without being engaged in the act of driving, without the adrenaline, I switch off. This is the key problem I suspect everyone at some level suffers from wether they want to admit it or not. Even awake, on full autopilot I suspect most people are in full-on daydream mode.
Really a conundrum - automation forestalls many accidents, but pilots get less hands-on experience and are less prepared to cope when the automation fails.
Excellent related talk by Capt. Warren VanderBurgh of American Airlines from 1997 (!):
https://www.youtube.com/watch?v=pN41LvuSz10
EDIT to add: some background:
https://99percentinvisible.org/episode/children-of-the-magen...
That, and very very strict oversight of every aspect from the design of aircraft all the way to maintenance is what aviation safe.
This problem has been studied to death in the airline industry. Surprising to see this repeated all over again.
Clearly it's possible to use these features in a way that increases risky distraction, but I think it's a mistake to assume such a driving mode can't be safer on net when used properly.
Definitely vouch for cruise control as having a cramping leg stuck on the accelerator for 5+ hours driving sucks but, personally, would say otherwise for lane keeping.
I can easily imagine there are people who can use lane keeping and radar cruise control safely, but I also know I am not one of them. I'll need to stick with manual driving until the car can drive itself in all cases.
This is the common case in pretty much all automated manufacturing plants where you have to hit the big red STOP button when stuff goes wrong. I don't quite see how its a failure when it has been working for them. In any case, do you have an alternative proposal that works?
Naturally there is always going to be human error, but it doesn't make sense to say "semi-autonomous" is bad while "full autonomy" is good. Guess what, we're going to have to deal with less advanced versions of the software before we can arrive at the real deal. The trick is to know and communicate the limits of the system. For example Tesla will alert you visually and through audio if you don't have your hands on the wheel. If it has to ask you three times, it'll just disable AutoPilot for the rest of the drive. It's just like a more advanced cruise control. If I hit a fire truck because I was on cruise control would anyone write an article blaming cruise control? No, because everyone knows the limits of that system. Crashes like this will force people to learn the limits of current autonomous software as well.
Better to completely remove the steering wheel, brakes and gas pedal than try for some half-way hybrid.
No human can stay alert enough to take split-second evasive maneuvers while doing nothing 3599 seconds out of 3600.
Perhaps Tesla, if the model has a camera, can detect where the drivers are - and if not consistently looking forward then alert them?
You know what's the solution? Don't use the feature if you can't use it. There are people that drink and drive, we didn't ban cars because of that...
If you can't achieve the same level of awareness or don't want to, well, too bad, don't use it. My SO stress when she drives, she is a good driver but she just doesn't like it. I'm pretty sure she will have enough awareness, but that thing will lower her stress considerably and will make driving much more pleasant for her.
That essentially means that it was. If it wasn't they would have denied it and released data.
> but its manual does warn that the system is ill-equipped to handle this exact sort of situation: “Traffic-Aware Cruise Control cannot detect all objects and may not brake/decelerate for stationary vehicles, especially in situations when you are driving over 50 mph (80 km/h) and a vehicle you are following moves out of your driving path and a stationary vehicle or object is in front of you instead.
Just for those unaware of Teslas previous handling of other crashes, this is them waving a huge flag saying "We fucked up and we know it".
I wonder how that call went "Hi Tesla, my self-driving car just drove head-on into a stationary firetruck" "Ohh... did you read the manual? It's supposed to do that, so it's basically your fault!"
What kind of ridiculous, half-assed logic is that? There could be any number of reasons they can't confirm this yet.
I haven't officially confirmed I'm not an alien being from a far away planet -- so that must mean I am one!
If Tesla's autopilot can't detect upcoming stationary objects, it should in the very least keep enough distance between itself and the vehicle ahead in order to allow the human at the wheel to have an unobscured view of the road ahead.
That changes the story a lot, do you know where you got that information?
It is entirely possible for the vehicle ahead to have an escape path to another lane but you to be pinned in your lane.
Our traffic laws don’t provide for a zero accident environment. They just reduce the damage and suffering to a level society will tolerate.
Suggested by tailgaters?
1) A two-second rule is insufficient.
2) You need more time if you can't see around or through the vehicle ahead of you (and various other reasons, like weather, road conditions, being followed by a tailgater, etc.)
California driver handbook: """ Most rear end collisions are caused by tailgating. To avoid tailgating, use the “3 second rule”: ...
You should allow for 4 or more seconds or when:...
Following large vehicles that block your view ahead. The extra space allows you to see around the vehicle. """
Does this happen frequently enough for you to ignore safety concerns? If so, you should be able to live(or not) with the tradeoff you are making.
Traffic flows best when drivers allow merges, not when they try to close gaps to prevent merges. Most aggressive mergers will quickly merge out as well.
You may even get some "thank you" waves...
Out here in the relaxed midwest most drivers in 60mph traffic seem to follow about 1.5 seconds.
It looks like highway planners expect to get 1900 vehicles per lane per hour at saturation, that averages 1.9 seconds between cars.
␄
† https://en.wikipedia.org/wiki/Two-second_rule (wherein it proclaims sleep impaired drivers in bad conditions should leave 6 seconds). If you think you need a six second reaction time, pull over and get out of the car.
And in any case, the 2 seconds is not the "suggested follow distance" it's the legal MINIMUM. That is, "You're clearly unsafe if following at any less than this," rather than, "Close up any gaps more than this."
Does Tesla's system have no optical sensors?
This is different from what happened in the tesla case. What happened here is that the vehicle in front of the car was moving and in view of the tesla's radar sensor obstructing the view of the firetruck. That car then moved and now a stationary object was suddenly in front of the car. From the Tesl's view point, an object just magically appeared somewhere in front of the car.
I'm not familiar with radar systems, but I imagine in this scenario the system isn't precise enough to know that this stationary object that suddenly appeared isn't an overhead sign or some other similar object that pops into the field of view of the radar system. It probably has something to do with radar not being extremely directional, constantly having stationary things pop up due to reflections and various objects in the periphery, having a limited sampling rate, and needing to do a filtering or other sorts of magic to make sure there aren't constant false alarms etc. I can see how cruising along at 50mph, the system doesn't have enough time to figure all this out and stop (e.g. not enough samples or there being a noise floor on stationary object data). It appears the correct way to solve this is with 3d lidar systems combined with sort of of mapping technology, but those are still too expensive/difficult to put into every day vehicles.
I'd had my Subaru slow due to a vehicle bumper sitting in the lane (from a crash that happened shortly before).
>Radar knows the speed of any object it sees, and is also simple, cheap, robust, and easy to build into a front bumper. But it also detects lots of things a car rolling down the highway needn't worry about, like overhead highway signs, loose hubcaps, or speed limit signs. So engineers make a choice, telling the car to ignore these things and keep its eyes on the other cars on the road: They program the system to focus on the stuff that's moving.
https://www.youtube.com/watch?v=FadR7ETT_1k
I guess this was in ideal conditions or maybe the Tesla in the firetruck accident doesn't have this software update.
1. Autopilot didn't leave a big enough gap in front of the Tesla. Presumably because the radar has limited range, or maybe it was a big enough gap but the guy just wasn't paying enough attention.
2. Autopilot ignores stationary objects. This is a deliberate decision - apparently if you don't ignore stationary objects there are too many false positives from stationary objects you aren't driving into (signs, bridges, etc).
The root cause of 2. is that the radar doesn't have good enough angular resolution to say whether something is in your path or not - it can just detect things vaguely in front of you. The solution is probably LIDAR (which everyone except Tesla uses) or maybe some camera-radar data fusion, but obviously it doesn't do that at the moment.
Not being able to tell if a stationary object is something you're going to hit or not (like LiDAR or stereo cameras might do) is more relevant to this case than maps.
Why is it unrealistic, besides the fact that you're following too close behind? If your line-of-sight is shorter than your braking distance, you are driving wrong.
Google shows two-second rule when looking for "safe following distance" - I was taught 3 seconds and it seems more reasonable assuming slightly over a second reaction time.
Basically, I rear ended somebody - but the details of why that happened are interesting to me.
I was going down a road I usually travelled to go to work that morning; two lanes each direction with a middle "suicide" lane.
Traffic was fairly heavy, as it always is in the area during morning traffic; there's a school not too far ahead in the direction I was travelling, and traffic "bunches up" and slows in the area, thanks to a crosswalk, people dropping kids off, and a "radar speed limit sign" that tells drivers how fast they are going in relation to the speed limit when school is in session (causes people to hit their brakes). Furthermore, not too far after the school is a stoplight for an intersection with another similar road.
Where I was at just before the accident was crossing a neighborhood street at a controlled intersection; also at that intersection, the suicide lane changes to an unprotected left turn lane.
So there I am, tooling along at my normal 40-45 mph (appropriate speed for the street I was on). Coming up on the intersection, a tractor-trailer semi was in front of me; the driver decided to make a left hand turn at the intersection, and got into the suicide-turning-into-a-left-turn lane. I decided to accelerate a bit to go around him. Now - I was kinda in an "autopilot" mode, not paying as much attention as I should have.
The traffic in front of me - thanks to the conditions I mentioned - which were typical of the morning time period, should have clued me in to "slow down" (which I have since taken to heart). That area, due to the traffic and conditions - is a "stop and go" situational nightmare. Traffic moves a bit, slows, maybe stops, starts again - and people do the typical: They don't keep their foot on the brake, so while they are "going slow" or even "stopped" (idling, not enough power to move) - their brake lights aren't "on".
So there I am - going around the truck - and "traffic ahead of me" registers, but I didn't see any brake lights, so while in my "autopilot" morning haste/haze/whathaveyou, I made the incorrect assumption that traffic ahead of me was moving; accelerating, maybe not going as fast as I was, but getting there. Which was the wrong assumption, of course.
The next thing I knew, I recall that the car in my lane ahead of me didn't have his brakes applied enough to turn his brake lights on, but wasn't moving anywhere near my speed; then he hit his brakes full (causing his lights to go on), and I slammed on my brakes just a bit too late in my realization. My speed dropped instantly, but not quick enough - I was probably going 15 mph or so when I rear ended him.
I was driving my 1996 C1500 pickup, his was a small crossover-like vehicle. Not much damage on my end; his bumper was mashed, lights broken, etc. We pulled over, exchanged insurance info, no cops involved, and went on our way. I called my insurance immediately, of course, and let them know what happened.
So it was a combo of things; my "autopilot" inattention, my speed, the traffic situation, the way people were "braking", going around a semi truck that was blocking my view then "road clear" ahead - it all came together in a "perfect storm", ending up with me rear-ending someone.
I tend to think that an autonomous car, or one with automatic braking (features not to be found on my truck at the time), would have been paying "more attention" and would have seen the car ahead of me not moving as fast (never mind the lack of brake lights), and would have hit the brakes and came to a stop much sooner. Indeed, had I been paying better attention, and going a bit slower (perhaps only going 30 or 35 mph), I could have applied my brakes much sooner, and avoided the accident.
Lesson learned, I guess.
Isn't this precisely the scenario that automatic emergency braking systems are designed to prevent?
The article suggests that no system can handle this, but the EuroNCAP system specifically tests cars driving at up to 80kph (~50mph) into a stationary vehicle (https://youtu.be/AJ4WXgWaNgs?t=2m40s protocol: https://cdn.euroncap.com/media/32278/euro-ncap-aeb-c2c-test-...) Is this sort of safety equipment not a "thing" in the US?
It looks like AEB is not fitted to the model S in the EU as standard. https://www.euroncap.com/en/results/tesla/model-s/7897 (expand safety assist section - no AEB listed, c.f. XC90 https://www.euroncap.com/en/results/volvo/xc90/20976)
I wonder if AEB was installed and activated in this crash, despite what the cruise control was doing? Surely it must have done otherwise I'd have expected significantly more damage, particularly to the fire truck getting a 2t lump slamming into it @ 65mph?!
So these car-mounted radar systems can't detect how large an object is or where it is in relation to the road? I don't get how they can be used at all then. That can't be true, right? Because if you can tell how large something is, then the hubcap is out. And if you can tell where something is in relation to the vehicle and/or road, then the signs are out. I mean, hell, the most maniacal situation of climbing a steep hill with clearance under a sign that you just can't see because the sign happens to be mounted just after the rise, which probably doesn't exist anywhere in the world, would be out by other factors, like knowing that you're going up a steep hill.
So it really sounds like the only thing left is just not being able to tell how large something is, which sounds wild.
> This unsettling compromise may be better than nothing
People frequently find disappointment to be worse than nothing.
It's why everyone else uses lidar instead, or in addition. Really, it has the same limits, but the wavelength of visible light is small enough that they're only an issue for microscopes.
See Subaru, Toyota, Honda, etc.
I'm not sure why this article and this discussion seemingly act like the predominant technology used in automatic braking systems doesn't exist?
The tech is still developing. We may be in a bit of a hype bubble, but it is as real and clear as it has ever been. I think even as the tech advances rapidly, public acceptance will be way further out than 5, 10 or 15 years. I would venture to say self-driving cars and truck fleets being normalized is 30 years away and in no way because of the tech, but due to all the red tape and public debate that will encase the issue.
If you think all truck drivers are going to be displaced in 5 or even 10 years, you may be living in an HN bubble. Sure jobs will be automated away, but this is going to take more time than lots of people think. For instance, one article like this could delay acceptance for months or years, in my opinion.
We change out our phones every couple years, but may car is five years old and I'm just about to finish paying it off. With a decade being a reasonable replacement cycle for a car, how will the car technology keep pace? Surely people aren't going to start buying iCars as often as they replace iPhones. Even if you adopted a service-only module for the industry, it's not like driving services will want to replace their entire fleet every two years.
Will cars have some sort of "technology package" including the computer and some of the sensor modules that can be made plug-and-play removable so you can upgrade your car?
I'm not sure how many people _really_ think that; it's pure fantasy. To be honest, I wouldn't be surprised if they're not obsolete in 20 years. AI stuff has a tendency to get nearly good enough quite quickly, and then improve very little more for decades afterwards.
What tends to happen is that some approach, deep learning in the current case, turns out to be very effective for a class of problems. But it turns out that it only gets you, say, 90 percent of the way there to being truly useful in the real world. And there isn't an obvious way to get you the other 10 percent.
https://en.wikipedia.org/wiki/Autonomous_cruise_control_syst...
I don't expect scanning lidar sensors to become common here until solid state scanning lidars reach mass production.
It's not a panacea of course.
But it would fix the firetruck problem pretty neatly, as professional vehicles will be required to stay maintained.
Also say the cars regularly ping each other for updates, then one car that was in sight and is still in sight disappears doesn't respond, then it gets flagged as a possible hazard.
Car related deaths are fairly common, I can't see any rational reason to not switch to autonomous driving as soon as they are statistically likely to save lives.
Do you really want a large (35,000 a year or so in the USA) people to die every year until autonomous cars are perfect? Not to mention nothing is ever perfect.
Doing your best and working towards safety is one thing. Putting 100% trust to autonomous thing is a different thing. If you know it's 100% safe, than it's rather easy to do. But if it's 98% safe.. It's pretty much gambling. You know it may fail and you have no chance to influence it. Sit back and hope you're not the (un)lucky one.
All of which is just to say that those voices pointing out the technical challenges are up against seriously desperate interests. This could get messy.
My guess is that you're right: level 5 will take about as long as it takes to get to photorealistic rendering - never quite there.
The only systems safe enough to allow fully automated vehicles in the near future will have to be on dedicated lanes or roads, probably with additional safety mechanisms on the roadway itself.
I think it's safe to say Autopilot was enabled. Tesla has never waited to rush out and state that the car's driver was lying and that their system didn't screw up. Presumably they will still blame the driver for not paying enough attention, but as the article says, not being able to detect a stopped emergency vehicle is a pretty giant gaping flaw.
Also, on the other hand not being able to recognize that your car is about to slam into a stopped emergency vehicle is also a giant gaping flaw on the driver's side.
Disclaimer to put my last statement into perspective: I have absolutely no relation to Tesla except for being a potential future customer. However I am driving a decent stretch daily and get to experience first person many stupid things people do in their cars due to ignorance/not paying attention/whatever, also I often use the adaptive cruise control of my Audi which shows me quite some false positives and restrictions (such as not letting itself deactivate below 15mph, heck, even deactivating itself without previous notification)
What always boggles me about such news is that people rely so much on these systems and apparently people drift away that they even don't notice an f*ing big red fire truck standing in their way. I often drive with dynamic cruise control (radar based, only keeping distance, breaking and speeding up, no steering), but I am in many situations in which I think "I need full control here" and temporarily disable it. Also, there are many situations where I don't use it in the first place because I know the way it functions is bringing downsides, such as driving on multi-lane roads (read: german Autobahn) since it will hold exactly that much distance to the car infront of me that every idiot will cut in, causing cruise control to decelerate to leave a bigger gap, rinse, repeat.
Maybe you're not a typical case?
FWIW, I consider myself a pretty decent focussed driver, yet when I hired a car with dynamic cruise control a few months back, I was shocked how much losing responsibility for part of the driving experience --the gears, acceleration, and braking, obvs-- helped me to relax too much, and lose a little bit of focus. I was still steering, and it wasn't like there were even any near misses... but I just felt my attention wander too many times for comfort.
Of course, I also notice that my focus changes a bit, but it still stays on the traffic around me and I would consider it rather improbable that I would oversee a stopped vehicle infront of me, not to mention a fire truck on a mission.
Maybe it's also that I'm driving daily in and out of Stuttgart, one of the main traffic spots in southern Germany. There's a lot of cars and ignorant driving, especially in dense traffic or jams. Plus we have a rediculous amount of roundabouts in the meantime and there are a lot of people that decide to either push into the smalles gaps, shooting in from your side and forcing you to do heavy breaking or other people approaching an empty roundabout, doing a needles near-full stop, accelerate, just to decellerate again, almost coming to another near-full stop to get around the corner (never understand the thinking behind this :-| ). I don't trust adaptive cruise control in either of these situations.
I don't understand your logic. Stationary objects either are rare, and wouldn't trigger too many false positives, or they aren't, and the car should be prepared for them.
I think the problem with this is to set them into the correct context. Around the road (and thus in the visible field of the sensors) you have A LOT of stationary objects such as houses, trees, traffic signs, roadside objects, parked cars, ... I think there is probably a big challenge determining which of these objects might be in the way and how to correctly ract to them.
Just as an example: Considering the situation the article and enhancing it a bit with guessings, it would have been the right decision to either stop or change lanes (depending on the road). However, if the car decides to change lanes and there is traffic on the other lane, we are in the same trouble of an accident due to autopilot again. Also, if autopilot decides to change lanes (or something similar in the category of "driving around") on a one-lane road (maybe even with missing lane marks), we might end up in oncoming traffic. Or what happens if the system falsely applies the decision to break in a turn with roadside objects (think of a 90° turn with a house in the corner). If the car falsely applies an emergency break here, our hypothetical car might be the one smashed into. Also, how do you set the thresholds for "stationary". If it is set too low, we might not stop infront of a stationary object until it is too late, if we set it too hight, we might stop way too early, say, in a traffic jam, again being the ones provoking accidents or more traffic jam due to unforseen heavy breaking.
I saw a tv program about self-driving cars a couple of years ago where the programmers said they would have it ready for major roads in a couple of years, but their human factors engineer said "a couple of decades", precisely because they realised humans would always be needed, and that the problem of transferring control back to humans while riding on the road hadn't been solved.
You are aware that this is literally how Waymo's existing taxi service in Phoenix works?
I am aware of the limitations, but the parts with "decades" and "delusional" are obviously overstated.
I can see how "this year" could slip into next year under unforeseen circumstances, but when your own prediction is so far away from the collective wisdom of an entire industry sector, it sure looks like a massive case of Dunning-Krueger, so you should have a very solid argument to support your prediction.
[1] https://www.theverge.com/2017/12/14/16776466/volvo-drive-me-...
Radar is just a very limited sensor!
A couple of other scenarios when adaptive cruise is on: cars changing lanes into the lane ahead of me at short distances do not cause it to react quickly enough. It seems there's too much lag in the time to capture the interloper; and, if I'm approaching a car quickly that is moving much slower than I and I signal a lane change but don't execute it, I'll collide with the slower car. (or so it seems to me, the system did not slow down and I had to apply the brake to avoid colliding).
Another related problem with vision-based systems, these random type of road artifacts that fool the system. This image shows a false left-side lane marker (formed by a partial re-paving and the shadow cast by the center barrier). It sounded a lane departure alert. If the car were autonomous, it likely would have swerved right trying to center: https://imgur.com/a/KnsXU
Even before reading this article, I have not been able to relax with my new automatic cruise control. The problem is that I don't have a solid intuition for it - so instead of relaxing, I remain nervous and alert while it is on. In reality, I use it way less than I used the vanilla system.
https://insideevs.com/elon-musk-tesla-doesnt-need-lidar-will...
https://9to5google.com/2015/10/16/elon-musk-says-that-the-li...
So it isn't that Tesla and volvo don't see a stationaty vehicle: they might not see objects as well.
Evil plan: you, in the front car, drive against a wall, and turn in the last second to avoid the collision. The autopilot behind you will accelerate against the wall.
Evil plan 2: you, in the front car, see a car/truck stopped in the lane. You waint until the last second to turn and avoid collision, the autopilot behind you will accelerate against it and crash.
No one is going to pay that much attention if your car is on auto-pilot. That's just how people are, no matter what's written on the manual (which no one reads).
Also the problem is a road sign or overpass over a crest of a hill. It's stationary directly in front of you, the road simply curves away.
EX: Here is a car in-front of a road sign. http://iowahighwayends.net/ends/June06/16/34exit263_99_halfm... We assume the sign is not on the actual road, and the software makes the same assumption. It's just not always true.
EX2: https://i.pinimg.com/736x/f7/11/eb/f711ebb462449a422151daab6... again perfectly safe but it looks like a static object blocking the road up ahead.
As big as a fire truck, and in the middle of the street, at the same level as your car!?
> Also the problem is a road sign or overpass over a crest of a hill. It's stationary directly in front of you, the road simply curves away.
Isn't the autopilot aware of where the street is, and knows that you are not going to hit it?
I'm not convinced.
Of course, I know there are a lot of much-smarter-than-me people working on this for years, but I still don't get it.
To give an idea individual letters can be 16" tall. http://onlinemanuals.txdot.gov/txdotmanuals/fsh/images/Figur... And sizes are rounded to nearest 1/2 foot.
Again here is a sample image. http://iowahighwayends.net/ends/June06/16/34exit263_99_halfm... Notice the road bleeds into the sign, but based on experience we assume the car is not about to hit the bridge at road height. It's a single image, so we are not using binocular vision to figure this out.
They're not at all in front of any car...
We can say they are not close enough to be a problem yet, but all I am pointing out is it's a harder problem than your thinking about with a lot of potential false positives.
I'm talking about maps + GPS (where is the road? will it curve in 50 meters?), and radar (what's in front of the car? how far is it? is it in the middle of the street, or on the side? Is it at the same height as my car?).
I don't see how these two tools together can make accellerating towards a stationary object in front of you make more sense than slowing down, or at least make some sort of sound to alert/wake up the driver.
Like I said, I know it's a difficult problems and very smart people have been working on this for possibly 20 years, but it still doesn't make sense to me.
Radar shows relative speeds, but can't distinguish between the road, bridge, and a stationary firetruck. It simply does not in any way help with this problem. (Radar useless)
LIDAR does what your thinking of, but Tesla does not use it. (LIDAR missing)
They use images, to avoid using LIDAR. So, now we have to detect stuff from images which is why I am showing you images. (immages only thing you have.)
But, for more distant objects a single pulse gives ever more crap the further out it travels. If you send 2 pulses next to each other you can adjust for vector of car and ignore the repeated data to just look for stuff moving relative to the background.
This results in really 'easy' automatic cruse control that ends up hitting stopped objects on the road.
PS: Things would get a little better if cars had one of those rotating arrays you see on ships, but car radar is a solid state system.
Also, they want to deliver value today, even before they can use most of their camera feeds, so state of the art today hopefully won’t be state of the art a few years from now: https://forums.tesla.com/forum/forums/how-many-cameras-are-c...
You are making assumptions about the placement of objects in the image, but the actual image in no way demonstrates the sign is not at street level.
On the other hand, while it seems that we're on the cusp of an autonomous vehicle revolution, and we'll see commercial use adopting early, consumers are going to be wary. The failure modes are very different than what drivers are used to. The systems appear "dumb" and make mistakes that humans rarely do. I see more promise in the short term for collision avoidance systems, or other systems which augment the driver's ability. For example anti-lock brakes have been an almost complete win, almost to the point of invisible ubiquity. I'd love to have something on-board my car that can help me safely avoid hitting a deer at 75mph.
I wouldn't hold my breath for that. Faster reflexes notwithstanding, automated systems don't change the laws of physics. If anything, I'd expect a human--at least during daylight hours--would be more likely to notice a deer at the side of the road and react accordingly before they ran in front of the car.
I say the same thing to the comments about the irresponsible “UX” of Autopilot for not handling this case. It’s more about irresponsible marketing, capitalizing on the enthusiasm for self-driving cars, potentially lulling overzealous customers to trust a cruise control system or emergency braking system with their lives.
Move fast and break things indeed.
There are a ton of datasets out there for things like traffic sign identification, and vehicle/pedestrian/etc identification - but most of those vehicles in those datasets are:
1. From the rear (or oblique rear angles)
2. Of mostly automobiles and small trucks
There likely aren't many real-world datasets of vehicles facing the vehicle and stopped in the road, and/or of larger vehicles (buses, semi-trucks/lorries, emergency vehicles, bulldozers/tractors, etc).
Without having such datasets, the AI you have trained won't have any way of knowing about those objects, and they may be odd enough that they can't be easily extrapolated from the datasets you do have to train on.
And by "dataset" - I mean you need massive amounts of data; 50,000 images would be a "small" dataset. Ideally you want many times that, plus you want to "generate" synthetic views for more training data (by skewing/warping the existing images, it helps the system generalize on the data).
That's a possible explanation, but I don't know if that's the reason, part of the reason, or no reason at all. Plus, it's not to say they are "at fault" - or to absolve the driver of any responsibility.
I'm just throwing it out there, based on my knowledge and experience - which isn't much, I admit (I completed the Udacity Self-Driving Car Engineer Nanodegree last year, plus Udacity's CS373 course, and what is now the Coursera Machine Learning course - but I took it as ML Class in 2011 before Coursera existed).
That should prevent all such trivial accidents and allows to actually mathematically prove that the software works, as it should be required for such a critical system.
Machine learning can be added for object detection to allow more sophisticated trajectory prediction.
I'll assume the latter: Even if you were able to perfectly maintain an accurate 3D model of the surrounding geometry (and associated trajectory of all moving objects), it doesn't mean you have enough information to make 100% accurate predictions. For example, a frozen over road often has very nearly exactly the same physical geometry and color, but extremely different behavior to cars trying to drive on it. Other weather effects like fog or snow bring their own challenges.
You're right though, that precise and accurate 3D models do do a lot to make driving easier and more correct, the problem is that the hardware necessary to produce those models is still very expensive (LIDAR). Most (all?) of the advanced self-driving prototype cars use LIDAR, while Tesla has decided that they can do without for their consumer models, sticking with just the simpler and less expensive RADAR and cameras.
In theory, Tesla's right, since humans get by just fine with only two "cameras", but we're clearly a long way from automating that level of performance.
Cameras alone seems unsuitable, since it doesn't seem possible to make a camera-based system that works correctly all the time, ideally provably so, as required for a life-critical system.
>But it also detects lots of things a car rolling down the highway needn't worry about, like overhead highway signs, loose hubcaps, or speed limit signs. So engineers make a choice, telling the car to ignore these things and keep its eyes on the other cars on the road: They program the system to focus on the stuff that's moving.
I don't know about the sensors on today's semi-autonomous cars but it seems like there's already enough data there to prioritize collision avoidance over forward motion.
It seems like the Wired story is very incomplete about the details. It needs a more "Ars Technica" in depth treatment or more ideally, an actual Tesla engineer to explain the self-driving computer's decision tree.
How do today's sensors that advertise their ability to "maintain distance" between cars work?
What's the difference between the following to scenarios to the front-mounted sensor?
- 60mph Tesla slamming into a slow-moving road cleaning vehicle at 20mph
- 40mph Tesla slamming into a stopped vehicle at 0 mph.
Isn't the ongoing computation of dy/dx to determine a "safe" gap between cars the same?EDIT to summarize replies with a possible technical explanation...
The resolution of the radar sensor treats overhead signs (like highway signs[1]) as being on the "same 2-dimensional plane" as cars directly in front of you. This would generate false positives. It's not 3D radar which would yield spherical data inputs of impending collisions. Without 3D data, you can't write a rule that ignores objects not 0 degrees in front of the car.
The resolution of radar treats surface level signs (such as the double-arrow[2] at T intersections) as being the same harmless mass as a stationary car. The low resolution cannot distinguish between the shape/footprint of small signs that are supposed to be there vs (large) stationary cars that are not. This object categorization requires LIDAR instead of radar.
Therefore, programming an unambiguous algorithm to prioritize "collision avoidance" is not possible with the current radar sensors. Is that an accurate summary of the technical limitations?
[1] https://www.google.com/search?q=overhead+green+highway+signs...
[2] https://www.google.com/search?q=2+direction+traffic+sign+dou...
Still do you want your car to directly hit a sign, litter or barrier? Why not have a second smaller system like the backup warning sensors most cars have to avoid hitting non-movable objects taller than 6 inches?
If I was at highway speeds and a bag blows in front of me? Yes I want to hit it. Slamming on the breaks might kill me.
Also note that despite all the hype surrounding those features you're still supposed to pay attention as a driver. Marketing and manuals tell very different stories here and the liability question is purely answered by the latter.
These two things are treated differently by a radar system - imagine you are driving in semi AV mode and you come around a turn and there is a vehicle on the side of the road stopped (i've been in this situation). For a hot second the car is pointed right at that fixed object and is probably still processing the lane curvature (if it can at all, some adaptive cruise systems don't have lane monitoring). The vehicle will ignore the fixed object and keep going as to not slam on the brakes which can be very dangerous.
I witnessed an accident very similar to this. A vehicle was partially blocking the left lane of a 4 lane highway. A pickup truck was traveling at highway speeds in the left lane. A small 4-door car was following the truck too closely.
The truck saw the lane blockage fairly late and performed an emergency lane change to avoid hitting the stopped vehicle. The small car behind the truck slammed into the stopped vehicle without ever even hitting the brakes. The driver was very seriously injured(the car battery was in her lap and most of the engine had entered the cab) but afaik survived.
That was my life lesson to always allow space between me and the vehicle in front of me.
Seeing that car plow into the stopped vehicle plays through my head routinely when driving.
Ignoring things that aren't moving is a standard technique in radar to prevent your returns from being swamped by, e.g., the ground instead of fast moving planes you're looking for.
The radar systems in these vehicles send out a radio pulse in a broad approximate-cone forward. They get bounces back from everything that reflects radio in front of them. Distance from the object is calculated by time between pulse and response. Speed towards/away from the object is calculated from Doppler shift of the radio frequency.
There are two main things that these systems can't detect.
1. Speed of the object perpendicular to the direction of radio wave travel.
2. Location of the object within the approximate-cone the radio pulse travels in.
Note that thanks to the second, you can't calculate the first with higher-level object tracking, either.
So the data you get back is a list of (same-direction velocity component, distance) pairs. There's no way to distinguish between stationary objects in the road and stationary objects above the road, to the side of the road, or even the surface of the road itself.
Radar just doesn't provide the directional information necessary to handle obstacle detection safely.