Live data from Hacker News

After 6 months of working fine, Tesla software update drives at barriers again

np.reddit.com

41–50 of 351 posts

Re: After 6 months of working fine, Tesla software update drives at barriers again

#41
post #28

Earlier quoted context omitted.

Why would any of that be relevant?

Because the same things that confuse humans can confuse computers that are largely trained with human data.

Millions of drivers per year use roads like this in California and Washington. They’re not very confusing for a human driver who’s paying attention.

Re: After 6 months of working fine, Tesla software update drives at barriers again

#42
post #16

I wonder how do unit tests work with NN (or if they're even a relevant concept at all). You could replay some testing video frames and make sure the objects are correctly identified, but i suppose that's already what training is about... If an issue like that resurface, does it mean that the original frames leading to the 2018 accident aren't part of the training (or at least frames from someone driving in this kind…

The frames from the 2018 should not be part of the training. They should be part of the test set to prove whatever training they do works.

Re: After 6 months of working fine, Tesla software update drives at barriers again

#43
post #16

I wonder how do unit tests work with NN (or if they're even a relevant concept at all). You could replay some testing video frames and make sure the objects are correctly identified, but i suppose that's already what training is about... If an issue like that resurface, does it mean that the original frames leading to the 2018 accident aren't part of the training (or at least frames from someone driving in this kind…

Yes, the problem is indeed that there's no real way to "look into" a neural network and understand how it has been trained. All you can do is observe that the given inputs generate the desired outputs.

Even if there was training based on the 2018 frames, that doesn't mean that you have verifiably fixed the problem. It's difficult to train a neural network selectively – every time you "train" the network with additional data, you are increasing the chance that you are also teaching it something you didn't intend which then can have a side-effect in some seemingly unrelated scenario.

You can see this in real life with image recognition networks. Teach them too much and they gradually become less effective at identifying anything.

Re: After 6 months of working fine, Tesla software update drives at barriers again

#44

Eventually we need the NTSB to certify updates before they are pushed out over the air. Similar to what the FAA does. These OTA updates are not ok for large machinery and endagers not only the Tesla driver but all others on the road.

Not eventually - now. This is putting everybody in danger, not just the owners of the cars.

Re: After 6 months of working fine, Tesla software update drives at barriers again

#45

Additional context: on March 23, 2018, a Tesla Model X, while using autopilot, drove into a barrier and killed the driver. This was fixed in a software update, but the issue seems to have resurfaced. NTSB analysis of the March 23 2018 collision: https://www.ntsb.gov/investigations/AccidentReports/Pages/HW... Tesla's statement of the March 23 2018 collision: https://www.tesla.com/blog/update-last-week%E2%80%99s-accide…

Well, it wasn't really "fixed" -- the driver is still dead.

Sure, if you construe the meaning of 'fixed' to mean 'roll back all events and time', which I don't think anyone expects. They probably fixed the software bug.

Re: After 6 months of working fine, Tesla software update drives at barriers again

#46

Earlier quoted context omitted.

I agree, but is there a way that could happen without slowing the process to a crawl? Depending on what’s involved it could easily push the gap between updates from months to years.

This is a feature, not a bug, and should be expected in life critical systems. Would you want Boeing to push updates out as frequently as Tesla does with the same sparse release notes Tesla provides (“bug fixes”) when safety system functionality is modified? Disclaimer: I own a Model S

This argument would be a bit different if we were losing 30,000 people a year in airliner crashes, instead of approximately zero.

Re: After 6 months of working fine, Tesla software update drives at barriers again

#47

Earlier quoted context omitted.

For a $700 car I might consider crazy compromises, but $70k+? Absolutely not.

That's what I find so interesting with Tesla owner. They spend a fortune on a car, then they minimize every single issue they have with the car. My explanation for this is that for a lot of owners, the car is a way to be part of a hyped group more than being a utilitarian object (what a car should be).

Happens with a lot of stuff, certain American-made motorcycles, for instance. You're in the club now, and the only way to stay in the club is to carry the manufacturer's water. In no case are we to admit that we spent a bunch of money on something that does a poor job of fulfilling its advertised purpose.

Re: After 6 months of working fine, Tesla software update drives at barriers again

#48
post #5

Earlier quoted context omitted.

Indeed. I have never understood the cheering for OTA of something that can literally kill you. Were they limited to infotainment and the useless easter eggs I would not care, however AP OTA is downright scary, especially pushed by vendor instead of being initiated by an informed user.

The AP can only kill you if you're distracted/asleep at the wheel and not paying attention. You're always in charge of driving the car appropriately, the "AP" can only provide tentative assistance of a very rough sort. It will try to guess at the control inputs you might want to provide (which does make things a bit more comfortable in the best case) but the actual control always rests with the human driver.

The issue is that the way the feature is designed and marketed makes it very easy for the driver to be distracted and not paying attention.

Re: After 6 months of working fine, Tesla software update drives at barriers again

#49
post #5

Earlier quoted context omitted.

Indeed. I have never understood the cheering for OTA of something that can literally kill you. Were they limited to infotainment and the useless easter eggs I would not care, however AP OTA is downright scary, especially pushed by vendor instead of being initiated by an informed user.

The AP can only kill you if you're distracted/asleep at the wheel and not paying attention. You're always in charge of driving the car appropriately, the "AP" can only provide tentative assistance of a very rough sort. It will try to guess at the control inputs you might want to provide (which does make things a bit more comfortable in the best case) but the actual control always rests with the human driver.

It shouldn't be marketed as 'Autopilot' then. Less informed people will expect it to do more than it can. It's (IMHO, criminally) misleading to market something as being capable of doing something it cannot do.

Re: After 6 months of working fine, Tesla software update drives at barriers again

#50

Scary... software developers at these robotic cars and their mistakes/bugs aren’t just going to bring down a business application(lose money) but kill their customers and innocent drivers. Progress to where it’s safer is going to be a killer and we the drivers on the road are unwilling guinea pigs to billionaires’ dreams/goals.

Unwilling? Don't buy a Tesla. Don't believe the hype. It's that simple. Granted, there is nothing stopping any ECU from killing you, but I'd trust a company like Honda way before Tesla.
Post reply on HN