I think this argues the opposite of what you think it does.
Monitoring != driving and if you had humans pesudo driving, the experience would be insanely bad cuz the human would be interjecting way too much.
I think this argues the opposite of what you think it does.
Monitoring != driving and if you had humans pesudo driving, the experience would be insanely bad cuz the human would be interjecting way too much.
https://waymo.com/blog/2024/05/fleet-response/
"the autonomous driver can reach out to a human fleet response agent for additional information to contextualize its environment. The Waymo Driver does not rely solely on the inputs it receives from the fleet response agent and it is in control of the vehicle at all times. As the Waymo Driver waits for input from fleet response, and even after receiving it, the Waymo Driver continues using available information to inform its decisions. This is important because, given the dynamic conditions on the road, the environment around the car can change, which either remedies the situation or influences how the Waymo Driver should proceed. In fact, the vast majority of such situations are resolved, without assistance, by the Waymo Driver."
But let's assume they're lying and you're right: what kind of throughput and latency do you expect to be required between the car and the remote driver for this to work safely? How does the car know if the remote driver is actually looking at the data and acting on that? What happens if the connection stutters? Does the car take control again? How would it decide when to alternate between remote and local control? What if the two sides disagree on what to do?