“It's a truck full of traffic lights”
twitter.com
twitter.com
With one huge exception: self parallel-parking.
I don't understand why this innovation doesn't get more love. Tesla's not the only manufacturer to offer this, of course, but this particular innovation has increased m enjoyment of city driving more than ... well, more than anything I can think of.
Even if they never get anything else to work, it would have been worth it just for self parallel-parking. lol
From an engineering perspective, of course there are serious problems that need attention, but sometimes it also good to celebrate the wins.
It's been in the Prius since 2003.
I agree. It's really nice to have the radar say "Yes, that space is big enough." and then put the car into it.
I'll still take that over the ones that beep proudly to tell you that they are about to fail to maintain their lane (hi ProPilot).
Not anymore, since they removed the radar. Rain seems to really interfere with the vision based system, and apparently auto high beams are required at night, and they flash constantly.
The high beams are a different story. I only like to use auto-high-beam on rural roads as they tend to be problematic on busy highways in Tesla and my non-Tesla. But requiring them even on highways would be a big problem that I don't foresee them solving soon. I'm worried that this is going to take a long time to fix.
IMO, they actually work pretty well on rural roads.
(Admittedly the reasons why the Subaru impressed me was more for its programming rather than absolute precision. I liked how smoothly it transitioned between following and open road ahead. Much less jerky.)
I think it was on the way out by maybe 2022
Short term: Global chip shortage made supply tight, and it was either remove it and rush out with the no radar code branch, or stop shipping cars.
Long term I think it's a fine decision, but short term it's kind of a big thing to rush.
That said, i want a cool fast BEV that makes highway driving easier. Right now, Tesla is the only option. A few others are close. If someone else beats Tesla to FSD with another system, I will be happy to go that way on my next car. Working FSD is worth a lot to me.
It was lost due to Tesla's decision to remove MobilEye as a supplier.
Mobileye generally focuses on highly optimized HW/SW that does individual things very well, in a manner similar to how factory automation works (e.g., they basically built a "lane keeping + auto-braking + sign reading" appliance).
Tesla decided that 1) It was bad to outsource automation 2) Starting from scratch and 'learning' how to drive using ML was better than iteratively teaching a car how to do discrete tasks very very well (this is why Autopilot regressed a bunch in 2016).
In general, it's another symptom of Elon's 'I have an extremely specific idea, let's figure out' mentality that sometimes works and sometimes results in useless tunnels under Las Vegas.
Edit: You can also accelerate without disabling it.
Hyundais have exceptionally-good lane-following.
Or maybe I'm just salty that my cruise control has never worked.
Eh? Yes they do. Bizarre lie.
LKA is just that, an assist, because if you let it drive it’ll bounce back and forth between the lane markers, not keep you seemingly centered.
Personally I see bumper to bumper traffic maybe 3 or 4 times a year (when driving home from a vacation or being forced to a doctor’s appointment during rush hour). And I honestly don’t get why anyone would subjugate them self to this kind of traffic as part of their daily commute.
In the NYC area, bumper to bumper traffic is common. It can be caused by an accident or construction that blocks one or more lanes, cars merging on to an already congested highway, etc. These conditions frequently happen even outside of rush hour.
You may have trouble understanding it, but empirically a huge number of people see this extremely regularly, if not daily.
It's not even necessarily a feature of horrifically long commutes. For one example, lots of places that have basically ok traffic have bottlenecks at bridges, you may be stop and go for a little while every day getting across that.
I used to live in LA where Santa Monica Blvd was always backed up. I doubt LA traffic has gotten better either.
I'm surprised by your insolence with regard to how shitty traffic circumstances are in big cities. Simply changing one's commuting times doesn't failsafe the issue.
Also, transit lines tend to connect well to mid-Manhattan but poorly between other locations. So if you live in Queens and work in Brooklyn, good luck getting to work reliably by public transportation. (Before you object to that arrangement, consider: If you own a house and have kids in school, you're not necessarily going to uproot your family and move just because your new job is further from home.)
Thus, many ordinary New Yorkers rely on cars to commute to work.
If you need to drive to the supermarket you should have the option of choosing a time and route with minimal risk of traffic jams. I find it hard to belief that many people are frequently hitting bumper to bumper traffics on their way to or from the supermarket. Occupationally yes, but frequently no.
1: https://www.google.com/maps/dir/84-25+168th+Pl,+Jamaica,+NY+...
The population of the tristate is nearly 20 million. Even a tenth of that is a lot of cars on the road.
In fact I’ve often heard people from that area complain more often about lack of parking near their commuter rail station. Which indicates that people do rather tolerate circling the parking lot in their park-and-ride rather then risking stop-and-go traffic jams.
Liability, insurance, legal minefields and plain old marketing would never allow cars ,that perform as well as the best performing cars do today, to be on the roads in "every day" conditions.
My conjecture is we end up building AV only roads. initially one lane of a highway, then ring roads round cities and major warehousing hubs, then across urban areas. Walled off in some way they simply become railways with benefits.
At that point every business model ever written with Self Driving in the title goes in the bin.
I am not saying the tech is useless - frankly it's fucking awesome that this is happening in my lifetime. But fucking awesome tech and workable business model aren't always the same thing.
Not sure where I am going with the rant but I sure hope we get more out of the billions spent here than Teflon.
The autonomous car business model is very much alive and well, it has simply shifted in two key areas that cause general consumers to misinterpret what is happening.
1) Use cases (ODD). Many people think "if I can't buy an autonomous car, it's not a real thing". But most manufacturers and AV developers other than Tesla aren't even trying to tackle that use case. Instead, the focus is on autonomous vehicles operating very profitably in specific locations and operating models that work. Heavy trucking on "easy" routes, ridesharing in well-mapped areas of the Southwest US, shuttles on popular metro and airport routes, etc. These use cases represent very large revenue opportunities and the tech development is progressing well.
2) Timing. Too many pundits and CEOs looking to generate PR buzz made ridiculous claims over the last few years about when autonomous vehicles would be ready. This set false expectations among the general public which has now soured perceptions since autonomous tech is not easy. Fully driverless is already ready in some very specific scenarios (ex. Waymo in Chandler) and is on track to roll out to more ODDs over the next 5-7 years. I can pretty much guarantee that you will see a significant number of fully driverless vehicles in suitable areas by 2030. No, they won't drive in upstate New York in a blizzard, but no one actually cares about that from a business perspective.
The other issues you raise - liability, insurance, legal roadblocks, etc. are mostly non-issues that already have solutions. The only one that's a continuing problem is the fragmented nature of legislation across different states. But there is very heavy lobbying going on right now to rectify this by the time it's actually needed.
Edit: I would be interested in real experts correcting my poor understanding of important subjects - can we talk ?
Close, but I think it's far more probable that we just whitelist roads / intersections / routes known to work well and be reliable--whether with a general-purpose or location-specific algorithm. There's still a ton of value shuttling people to and from the airport and local hotels.
Then there'll be incentive for local restaurants to also be included in the available destinations, so there'll be pressure to both improve local roads / intersections to make them more easily navigable by self-driving cars, and on self-driving cars to get better at navigating them. With time, the locations / routes that self-driving cars can reliably reach will expand until it covers the vast majority of desired destinations.
We actually are following the same pattern with the horses -> cars transition. There are still plenty of places that cars can't reach and horses can. Over decades, though, we just kind of paved roads everywhere anyone really wanted to go. Nowadays it's more or less a given that if you want people to be able to reach somewhere, it'll need to have a road.
We'll see the same thing with self-driving cars. There'll still be roads that self-driving cars avoid and humans drive on, but they'll become less and less relevant as the value of self-driving cars becomes more apparent.
You might say people don't want those delays but we tolerate delays in normal commuting. An unattended bag on a tube station stopping trains, a car accident blocking traffic, traffic jams blocking traffic, mechanical breakdowns, etc. As long as they're infrequent enough, it should be OK for riders.
That's not happening any more. All we have left is laughing at stuff like this, where the visualization (not even the autopilot!) gets confused by seeing real (!) traffic lights on a truck, so it paints them in space, but then has to re-recognize them because they are moving.
At some point, the luddites will just run out of ammunition. It's sort of happening already.
But the AI drives slowly and gets confused easily. Regular drivers routinely have to go around self-driving cars. Not to say they won't improve, but it seems like current AI is assistive to the point where it might be harmful when drivers rely on it in speeds and situations where they shouldn't. I'm sure it will keep improving, but I feel like this is one of those situations where the amount of data and training required, and the amount of iteration on the software required to handle edge cases is not impossible but is exceptionally difficult.
If you want to fix this one exception (false positive) you will introduce unwanted false negatives. That's how precision and recall work, there's a trade-off. So I am not sure it's useful to fix it, how many times does this happen? Will fixing it introduce more frequent bugs?
Probably better to say that the AI drives slower than you would and gets confused differently. Real drivers die every day to terrible mistakes that look obvious in hindsight. Most of them probably thought AI was terrible too.
The bar here is much lower than you think it is, and frankly existing automation has already crossed it.
Just my hypothesis: but I think the autopilot really did see them as traffic lights, and just got lucky that they weren't powered and ignored them as out of order. Were there a cross street, I suspect the car would have stopped and treated it as an uncontrolled intersection...
But the software model is that traffic signs are static, and these were moving, so the visualization had no way to present that. It just left them there until the ML told them they weren't there anymore.
What would the AP have done? We don't know. But I don't know why we should simply assume it would have done the wrong thing. Driving is filled with false-positive indicators that it already knows to ignore successfully.
Will you bet with your life on it?
The individual still thinks in terms of "I'm an above-average driver, I'm better than a silly bleep-bloop box." They'll resist self-driving en masse if it's not 1000% perfect.
Insurers, however, will see self-drivers as predictable, never drunk, always following the speed limit, and in aggregate preferrable to humans. They will be able to see "3% better" as meaningful even if it's not perfect, and price accordingly. Eventually, you'll pay a rapidly increasing penalty rate for having a steering wheel. This is where the avalanche comes from.
I also figure self-driving could unlock new features-- in particular I'm imagining the only way we get road speeds much over 120kph is self-driving, as the human response time becomes a limiting factor. And of course the in-dashboard wet bar. This will feed back into the consumer market even if it's only closed markets at first: why can't I go 250kph on the highways considering the self-driving airport shuttle does?
Time and again I've watched "ain't happening" technology become the preferred norm practically overnight. Eagerly awaiting my FSD CT, and making long trips without having to micro-manage every foot across thousands of miles.
sadly, in India too, the major electric 2wheeler Ather, is kinda going the same high-tech way as Tesla. and very expensive !
A big part of Tesla's success was making electric vehicles that were covetable, rather than being obvious "we made this for compliance reasons or to get a government contract" products. This means targeting a luxury market segment. The way they chose to wow luxury consumers was with high performance and a lot of technological gimmickry.
That would be awesome still and make people want to have that technology...how does that murder Tesla's business model? Waymo would easily pivot to licensing their tech to car manufacturers.
It seems like they should have a million hard test cases that must pass in simulation before releasing a new model. The simulations should be harder and more extreme than anything encountered in real life.
I think the real problem is obvious. They're trying to rush the work because Elon said so.
The car is properly recognizing traffic lights pretty darned well, considering the circumstance. It looks like it has a built in understanding that traffic lights are "always" stationary - hence, assigning them static locations on the 3D map - but it keeps having to update the model because the lights are actually moving.
This seems like a very non-obvious edge case that I wouldn't expect an ML team to even consider as a possibility. Now they need to program into the ML model an understanding that traffic lights are typically stationary. Which seems even more difficult to me, from a technical perspective - you don't want false negatives...
The car isn't braking or making any strange maneuvers from what I can tell. I'm actually impressed that it's handling it this well.
When you don't know what to do - do nothing. What if it was a traffic light on roller skates? Or a kid, dressed as a traffic light, on roller skates?
Collision detection systems (radar) are accurately not detecting an impending collision because the lights are not actually on a collision course with the vehicle.
Object recognition systems (computer vision) are working very well, because they recognize the lights and are updating the 3D map accordingly, but the traffic light 3D model is not designed to be a moving object - unlike vehicles, which frequently move. Which is why we see the car "passing through" them.
What we are likely seeing is simply a weird edge case in the output for the user-interface. I'd imagine if an object was actually flying at the car and the car could see it, it would brake accordingly.
Also, the map is two-dimensional. The car frequently drives underneath traffic lights that I'm sure also appear "on top of" the car in normal cases.
Object recognition and collision detection, from what I understand, are two very different systems.
But seriously, I’m inclined to be charitable here and assume that this is merely a quirk of the UI display. There’s no evidence that the autopilot did anything unsafe (apparently it wasn’t even engaged?), and until I see evidence of that I’m willing to withhold judgment. (I have seen evidence of other situations where Tesla autopilot did unsafe things and I’m in no way apologetic about those situations.)
In this case, obviously it's not a safety concern because the object is being hauled on the back of a truck.
They don't work there anymore.
From their experience, I know one thing: I will never work for Elon Musk. He may be a great visionary and salesman, but he's a horrible manager.
I know it's cool to hate Elon.
If you want evidence from a reasonably neutral observer, take Sandy Munro (himself an engineer who has worked on everything from cars to aeroplanes). He recently interviewed Elon, ostensibly about Tesla but the interview was in a meeting room at SpaceX. After the interview he was invited to a two hour design review meeting and was "blown away" at Elon's depth of involvement.
https://youtu.be/S1nc_chrNQk?t=370 (6:10 to 8:45)
Sources: https://www.reddit.com/r/SpaceXLounge/comments/k1e0ta/eviden...
It was stunning to see the complete disconnect between Musk's grand declarations and what the organization was actually setup to deliver.
Frankly, it just gives me more respect for Tim Cook, who as COO at Apple made his company able to turnaround and deliver HW in record time.
Edit: in retrospect I wonder if Musk's grand public declarations were actually a way to control and pressure his own organization. Remember, Musk didn't actually found Tesla, he rescued it from bankruptcy after the Roadster didn't return as much as needed, so he inherited an existing structure.
Yes. The human brain and visual systems aren't nearly so trivial to replicate as a lot of people in the tech industry seem to think.
Tesla is just one of many case studies in the paired tech industry arrogance seen so frequently:
- "A human is just a couple really crappy cameras and a neural network, we know how to do better cameras and neural networks, how hard can it be?"
- "We can do anything we dream with 99.995% reliability in the synthetic, computer-based world of the internet because we know code. Therefore, we can do anything we want in the physical reality with code!"
Both are far from evident in practice, but the belief in them continues, despite it being increasingly obvious to everyone else that neither one is true.
Human vision and world processing is quite impressive - and, as pointed out elsewhere in this thread, a two or three year old would have no trouble working out that the obstacles were some things on a truck. I've got a nearly three year old, and I guarantee he wouldn't confuse those for stoplights in the slightest. I also wouldn't let him out on the road, though he does well enough with a little Power Wheels type toy. But there is far more going on in the visual processing system than we even understand yet, much less have the slightest clue how to replicate.
And while code may be fine on the internet (where you can retry failed API calls and things mostly make sense), the quote about how fiction is constrained by what's believable and reality sees no such restrictions is very true. Out on the roads, all sorts of absolutely insane things can and do happen on a regular basis - and you can't predict or plan for all of them. But the car has to handle them or it crashes.
As a random example, a year or two ago, I was behind a car that had poorly strapped a chunk of plywood to their roofrack with a good chunk hanging forward, and the front end of it was starting to oscillate awfully hard. I had a good clue that it was going to come apart sometime in the very near future, so backed off from a normal following distance to quite a way back. Sure enough, half a mile later, it failed, went flying through the air, slammed into the road a good distance behind the car, and tumbled a bit. Had I been using a normal in town following distance, it would have either hit me or tumbled into me, but using a human visual system, it was obvious that my existing following distance stood a good chance of being a bad idea.
Stuff like this happens on roads constantly. Meanwhile, state of the art self driving can't tell the difference between stoplights and some poles on a truck. You'll excuse me if I don't think the problem is anywhere remotely close to solved for a general case Level 4 purpose.
Aritical neural networks are pretty good at object recognition, among hundreds of other things, and even better than humans at some of them. They are, however, generally pretty bad at abstract reasoning, critical thinking, 'understanding' concepts in-depth, and so on, and I think that's a more constructive way to phrase the problem we see in this video.
When a problem is fully redicible to a simple vision problem, modern neural networks are a great choice, but being a good driver involves much more than just the visual cortex.
One way to think of this is that that the footage is implicitly labelled: we have the benefit of hindsight: we know what the state/location of the vehicle was going into the future. That benefit of hindsight also can serve as implicit labels by knowledge that the vehicle did not crash or collide with something immediately after the footage.
I don't understand why this is hard for Tesla engineers -- I was doing this kind of thing in grad school a decade+ ago and it worked fine. I've seen it in other demos where object classifications rapidly cycle between person, bike, car, etc. Are they not filtering anything? Is this a symptom of "AI-ing all the things"? Because we did it with bog standard computer vision techniques back then and never got behaviors like this.
Move fast and break things [like tests]
(the steering wheel icon at the top of the screen is grey, not blue)
I also remember being at an intersection where I was turning left and was waiting behind another car. The display repeatedly showed cars the cars crossing in front of us crashing into the car in front of me. Not sure why.
It works much better now, but it was always kind of amusing. It only did it when we were all stopped. Moving cars (whether it was them moving or me) were rendered just fine. My guess is that it was extrapolating movement based on more than one "frame" of sensor data, but at a stop there's no changes beyond noise, and the noise was being extrapolated into extreme movements.
I have seen it show cars "crashing" into me, but it's only semis when in the neighboring lane.
Except we're trusting ML to perform surgery, choose conviction sentencing, evaluate job CVs, determine acceptable marriage partners (why not?), determine who can have kids (why not?), determine who gets into college (why not?), determine who gets a loan (why not?), determine who gets to work on ML (why not?). And drive cars.
> The data subject shall have the right not to be subject to a decision based solely on automated processing, including profiling, which produces legal effects concerning him or her or similarly significantly affects him or her.
https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CEL...
Question on your snippet though. It says "subject to a decision based solely on automated processing ..."
Since I do live in the consumer's paradise I'm naturally suspicious. I wonder if people will sometimes be subject to decisions based solely on automated processing, and if they don't bother to ask for a human in the loop after the automated decision, then that's that.
And how would you even know, one way or the other?
Another example is roads, where the design of the road allows one to turn into an opposing vehicle. The road itself is not deciding to turn your car into a semi trailer because it looks like sky, but an ML driven car has, multiple times.
I don't even own a Tesla, and I resent having to participate in its beta program. ML in a car is quite different from a brake recall, or even a stuck accelerator software recall.
It's only a matter of time before the software in these cars can handle the vast majority of edge cases as well as or better than human beings. Human vision isn't exactly reliable.[a]
In the meantime, someone should make a playable game in which trucks throw street lights at cars. Maybe someone at Tesla is willing to make this game in good jest?
[a] See, for example http://www.ritsumei.ac.jp/~akitaoka/index-e.html
We discount how much the concept of “understanding” is required in visual perception. We don’t just see shapes we have a complete understanding of what we’re seeing.
I might see a big rectangle flopping in the lane in front of me. I can immediately ascertain whether it’s a piece of tumbling plywood, or foam based on movement characteristics, color, apparently size, etc. I can then use that understanding to decide what evasive actions are required.
A Tesla it seems has absolutely zero of this capability.
It was a tow truck towing a car backwards. It was just enough in my half-asleep state to scare the shit out of me.
Humans have millions of years of evolution behind our visual processing systems. We have developed hacks that prevent our brain from getting tricked by unusual situations like traffic lights on trucks or backwards cars being towed. We only developed the first computers a hundred years ago, and only in the last 40 years have a small subset of people started learning about visual processing systems.
It's easy to look at this video and scoff because of how trivial it seems. But it's instead a marvel of our minds that we can pick up on context clues so quickly and accurately that such oddities basically never puzzle us. Given the pace of our innovation, it wouldn't surprise me if our computer systems match ours within a few human generations at latest.
There are some funny(?) youtube videos of people in the passenger seat waking up to this with tractor trailers being towed in reverse.
This is not a FLOPS problem. Moore's law can't save you here.
And you're sure that it was a bump, and not the driver pulling up rather close behind it and then giving a sharp tap of the brakes to wake you up? ;)
As the second video in the thread demonstrates, the truck is literally hauling traffic lights. The AI recognition is correct, the only thing worth complaining about is that they're displayed as static objects for the user after recognition, just to be re-recognized a few seconds later in a different place. Note that the car is correctly not detecting they are lit, so not inferring direction (though AP isn't engaged, so I guess we'll never know what it would have done).
No doubt you could play the same game by putting a traffic cone on your bike. The car wants to see important traffic objects, it's literally what it's trained for.
UI bugs aren't blockers for mythical SAE Level 5 Autonomy. You just... fix them.
In many places, the road rules say that if you see a broken traffic light, you should treat it as a stop sign. So a theoretical L5 car should have stopped there, in the middle of the road -- and again, and again. Seems pretty bad to me.
And yes, I agree that you "just.. fix them" -- but of the difficulties of the real road driving is that the number of unique situations like that is very large, and many of them would not happen during test drives / development.
I think it's not an actual problem affecting the driving because the driving was unaffected. Autopilot wasn't engaged, we don't have evidence.
I'm just pointing out that the autopilot doesn't drive by reference to the dash UI (which is showing a pretty obvious visualization -- the UI understands these to be static objects so once it gets one it "animates" it as if the car was passing it), so bugs there aren't very informative as to its behavior.
Tesla now has data about what it looks like to drive behind a truck transporting traffic lights! No team in the world would solve this problem, in advance, in simulation.
Not saying their strategy is going to work, not saying it's an unbeatable advantage, but: just look at it! This is a compelling demonstration.
But it clearly means another edge case like detecting deer (wonder if they can handle our local Kudu) that they need to deal with.
They might as well develop AGI at this rate.
(the grey steering wheel icon means autopilot is not engaged, it would be blue if it was on)
It would generally be a clue that there's an intersection busy enough to require signals that now lacks signals or signage which would warrant extra caution. I'd expect the car to at least slow down significantly, if not come to a complete stop before proceeding.
Somewhere at Tesla there's a junior engineer who's telling a senior engineer "I told you so!"
But seriously, these are just slightly funny obscure weird cases, imagine when the hackers start coming up with malicious cases to mess with these cars.
The odd thing is that even a randomly stupid AI for self driving is statistically safer than most drivers. Clearly there is a ton of room for improvement in both AI and Humans.
A strong claim, lacking actual evidence for it. All we have to go on are some Elon tweets (rather the definition of a biased source) and the actual crash rate. Without a lot more data (which Tesla steadfastly refuses to release) about environments, corrections, etc, it's quite impossible to make that sort of statement with any confidence.
The Tesla hardware is a weird combination of capable and insanely dumb, and it's far from obvious which it will be in any given situation until it's gone through it.
If an honest statistical analysis of the data indicated that Tesla's automation was better than human drivers (or better than other driver assist systems), I would fully expect them to have released the values. Since they haven't, and only hint at it and make statements that sound statistical but really aren't, I assume they've done the numbers internally and know it's not nearly as good as they like to imply.
If I drove in a city like their "self driving" beta was a few months back, I would be hauled from the car on suspicions of driving while hammered.
This hasn’t been shown yet at all. Statistics showing autopilot have less crashes per mile always ignore that Autopilot is doing the type of driving that has the least accidents per mile (motorway driving).
the fact that people still trot this out every Tesla thread is super annoying. Sorry to break it to you but this is a 100% false claim
https://www.forbes.com/sites/bradtempleton/2020/10/28/new-te...
I think self driving is a typical 80/20 problem. We won't have "full" self driving because the costs are exponential for each step closer to it. But driving on 80% of roads on 80% of days, with supervision? That could happen.
But that said: we won't accept AI that just makes traffic safer "on average". I'm fine with human shortcomings causing accidents. People will not accept car manufacturers cutting corners and causing accidents, even if statistically it's safer. So the very high bar for self driving isn't just "as safe as humans".
I'm sorry, did you mean customers?