> otherwise you can't react
I'm far from neuroscience, but humans don't need to operate at 20Hz to drive a car. And human reaction latency (event to measurable action) is often over 1s (under 1Hz).
I'm far from neuroscience, but humans don't need to operate at 20Hz to drive a car. And human reaction latency (event to measurable action) is often over 1s (under 1Hz).
From what I understand about AV (as a non-expert!), all three of those steps happen at different clock rates, ie you have a planner that’s updating continuously with observations from sensors at one rate, that planner then issues actions that get picked up by the actuators at another rate.
In that sense 20hz should really be compared to human reflexes without perception and planning; in scenarios where one is anticipating an action, response time can be as low as 150ms. in that context, I think 50ms/20hz is plenty reasonable for an automated driver.
Though you can't convert between hz and latency, all 20hz tells us is that it adjusts 20 times a second, not how long it takes from sensor input to be fed into a particular choice of adjustment, there could be (and actually almost certainly are) multiple adjustments in flight simultaneously with the adjustment actually being applied being calculated from old data (both in humans and automated substitutes).
This is not a helpful statement unless you can claim what speed human sensors do work at. And it's going to be faster than the latency of $(sensor + server round trip) Hertz, not getting into LLM processing time.
In humans, it's about 200–250 ms for a visual cue where you already know how to respond and you're ready, but you don't know exactly when it'll happen. It can be a fair bit longer if you need to identify what you see and choose how to respond. Typical perception to reaction time estimates for drivers when there's an unexpected hazard on the road are 1-2 seconds.
I mean, consider competitive video games. Humans who play a lot and pay attention respond to stimuli much faster than 250ms.
There are a lot of reasons people could sometimes react faster (for example, if they anticipate the hazard, or if they're just above average in reaction speed), but one to two seconds is the reaction speed we find most of the time.
The fastest human reactions aren't to unexpected road hazards. We have a much faster reaction speed in tests where you just have to click the mouse each time the screen flashes. Our reactions are fastest when you know in advance the event is about to happen. But this isn't relevant for road safety.
Like just running a first pass sanity analysis on the 1-2sec timeline fails because if it were true in practice all those idiots who screech about how normal traffic doesn't keep following distances worthy of semi trucks to the traffic ahead would be proven right as every braking event would cause a pile up. So either humans react much faster to the unexpected (not likely, we've measured) or humans have a huge "context window" for what to expect that makes the 1-2sec number not relevant in the base case.
Your close following distance example doesn't show anything. A normal braking event on the highway doesn't require a fast reaction. If you're driving 100 km/h and you're following 1.5 seconds behind the car in front of you (about half the recommended following distance) and they brake to 80 km/h, you have about 9 seconds to slow down or switch lanes. That's plenty of time.
The risky scenario is if the car in front of you has to do a full, hard emergency stop and you're following too closely. That's rare, and collisions are common when it happens.
If you know the car in front of you is going to brake because you can see the traffic ahead slowing down, that's not fast reaction time. That's just you seeing cars slow down and reacting at a normal speed. An AI has just as much time to react to that as you do.
This is so self evidently false, I struggle to believe you think it is true. How could anyone catch a ball even?
it works because 99% of the time you don't need fast latency because you can accurately predict things.
that's why a standard recommendation is to drive 2+ seconds (time not distance) behind the car in front of you. also why experienced drivers instinctively move their hands/feet into position during tricky moments when they need to cut the latency.
fun exercise, try taking your foot off the gas and hitting the break - slower than you think!!