Driverless robotaxi fleet paralyzed for hours in San Francisco

I would be surprised if that were the cause. Fine localization should be able to resolve without GNSS input (with caveats) and there are specific tested requirements to be able to tolerate a certain number of minutes of outage even in the absence of LIDAR before position accuracy degrades beyond acceptable limits. It may be an edge case in the GNSS pipeline, but I don't think it's that edge case.

Re: Driverless robotaxi fleet paralyzed for hours in San Francisco

#6

Post by ra7 » Thu, Jun 30, 2022, 11:56 PM UTC

AlotOfReading wrote: post #5

CTDOCodebases wrote: post #2

Could this just be a simple case of GPS jamming?

Background: I formerly worked at Cruise and specifically wrote large parts of the GNSS data pipeline. I would be surprised if that were the cause. Fine localization should be able to resolve without GNSS input (with caveats) and there are specific tested requirements to be able to tolerate a certain number of minutes of outage even in the absence of LIDAR before position accuracy degrades beyond acceptable limits. It…

Could this be due to bad mapping data at that particular location? Even if it was, wouldn’t they be able to pull over at a safe location with what they perceive in real time?

Re: Driverless robotaxi fleet paralyzed for hours in San Francisco

#7

Post by kzrdude » Fri, Jul 01, 2022, 12:04 AM UTC

gvb wrote: post #3

CTDOCodebases wrote: post #2

Could this just be a simple case of GPS jamming?

Could be but a much more likely cause is a software update that went bad. Likely the cloud rained on them.

I would not want a car that's updating during a ride

Re: Driverless robotaxi fleet paralyzed for hours in San Francisco

#8

Post by apstats » Fri, Jul 01, 2022, 12:05 AM UTC

People may get annoyed at cruise for this, but imo it’s still not as bad as the constant blocking of bike lanes and stopping in the middle of the road by human ride share drivers.

Re: Driverless robotaxi fleet paralyzed for hours in San Francisco

#9

Post by a9h74j » Fri, Jul 01, 2022, 12:06 AM UTC

kzrdude wrote: post #7

gvb wrote: post #3

Earlier quoted context omitted.

Could be but a much more likely cause is a software update that went bad. Likely the cloud rained on them.

I would not want a car that's updating during a ride

Future taxis or rentals: Bring Your Own Firmware

Or: Backseat driver via bluetooth, phone to taxi.

Re: Driverless robotaxi fleet paralyzed for hours in San Francisco

#10

Post by xyst » Fri, Jul 01, 2022, 12:07 AM UTC

all of this time and money wasted on driverless cars has been a complete failure.

companies and cities should be investing their time into improving public transportation and designing our cities to be more walkable and make alternate modes of transportation more feasible. the US culture of using a car for everyday transportation is fucking insane, wasteful, and contributes to the rising cost of living across the US (not just SF).