If self-driving vehicles are tested on public streets, all data generated should be public. Companies should be cooperating, not competing, on "don't hit telephone poles" and "don't run over children".
Waymo issues software and mapping recall after robotaxi crashes into a pole
31–40 of 43 posts
Re: Waymo issues software and mapping recall after robotaxi crashes into a pole
#32"Recall" really needs to be retired as a term.
What'd be the proper term then? In french when, for example, many cars are sent back to the dealerships (or factory) to fix something, it's called a "campagne de rappel ("recall campaign"). P.S: I've got nothing against "recall" being recalled so that it can be fixed ; )
While I have previously agreed that it should not be necessary to change the term, it is unfortunately confusing to laypeople and intentionally misconstrued by bad actors to downplay safety faults. I propose it should be replaced with: “Safety Defect Notice” which is a fairly precise description of the underlying concept and can not be misconstrued to be about the “fix”.
Re: Waymo issues software and mapping recall after robotaxi crashes into a pole
#33If self-driving vehicles are tested on public streets, all data generated should be public. Companies should be cooperating, not competing, on "don't hit telephone poles" and "don't run over children".
[flagged]
Re: Waymo issues software and mapping recall after robotaxi crashes into a pole
#34This is the most interesting part, in my opinion: > Waymo’s recall was deployed by the company’s engineers at the central depot where the vehicles return for regular maintenance and testing. It was not through an over-the-air software update, like some of Tesla’s recent recalls. I'd be interested to learn more about why the updates are manual, and also whether the map data is fully local to the vehicle. Tesla obvious…
It sounds weird to say, but updates being applied only in-garage doesn't mean they're not going over the air. However, updates can include software for between dozens and hundreds of individual processors. That makes them quite large. The real data pigs are driving logs and map data though, which are usually serious storage constraints in autonomous vehicles.
In fact, it's probably fastest to have a small bank of hard drives that you can physically pull from the vehicle and swap out for a fresh one. You could probably pack a few hundred TB of storage into a unit that could fit in a briefcase and have it loaded with fresh map data and lots of room for logs.
Re: Waymo issues software and mapping recall after robotaxi crashes into a pole
#35Earlier quoted context omitted.
It sounds weird to say, but updates being applied only in-garage doesn't mean they're not going over the air. However, updates can include software for between dozens and hundreds of individual processors. That makes them quite large. The real data pigs are driving logs and map data though, which are usually serious storage constraints in autonomous vehicles.
Yeah, I can definitely understand that it's probably far faster (and cheaper, and reliable) to transfer the data in the shop with a USB cable in both directions. In fact, it's probably fastest to have a small bank of hard drives that you can physically pull from the vehicle and swap out for a fresh one. You could probably pack a few hundred TB of storage into a unit that could fit in a briefcase and have it loaded wi…
Re: Waymo issues software and mapping recall after robotaxi crashes into a pole
#36If self-driving vehicles are tested on public streets, all data generated should be public. Companies should be cooperating, not competing, on "don't hit telephone poles" and "don't run over children".
Sounds cool in theory, but much less than useful in practice. The hardware and file formats are different enough that the data would be mostly useless to us (I work at a self driving-ish company). The models are predicated a specific set of hardware ( which camera, what fidelity LiDAR, but even something as simple as “what’s the frame rate” can have a difference)
Re: Waymo issues software and mapping recall after robotaxi crashes into a pole
#37Earlier quoted context omitted.
[flagged]
Just annoying how it's always privatize the profits, socialize the risk.
Re: Waymo issues software and mapping recall after robotaxi crashes into a pole
#38If self-driving vehicles are tested on public streets, all data generated should be public. Companies should be cooperating, not competing, on "don't hit telephone poles" and "don't run over children".
[flagged]
Re: Waymo issues software and mapping recall after robotaxi crashes into a pole
#39Earlier quoted context omitted.
Just annoying how it's always privatize the profits, socialize the risk.
The companies doing the mapping and algorithm develop do face significant legal and technical risk, and they’re unlikely to be bailed out. Perhaps the public is facing some safety risk, but this isn’t what was usually meant by your idiom of choice.
The corporation will yield net profits from this, and the people will suffer the losses from this. That seems close enough to the idiom, in my view. But i'm no expert.
Re: Waymo issues software and mapping recall after robotaxi crashes into a pole
#40" The update corrects an error in the software that “assigned a low damage score” to the telephone pole." What did it get classified as? What's a Waymo allowed to hit?