4 ms·
It sounds to me like you don't understand how little performance you actually need for this kind of stuff. People have been writing effective autopilot software
by BugsJustFindMe 8y ago
It sounds to me like you don't understand how little performance you actually need for this kind of stuff. People have been writing effective autopilot software for decades using hardware that wasn't even particularly fast at the time and may as well be a pile of sand today. What exactly do you think that that code needs to do? I promise that Python on a new smartphone can do way more now than we could do 20 years ago on a Pentium in C or C++. You're lucky if any of your sensors emit at even 100Hz.
- maym86 8y agoI think OP's point is about the latency from all the layers. At 70 mph, where 100ms is 3m, this is a problem for a control system.
- commaai 8y agoHuman latency is about 250ms.
- deleted 8y ago[deleted]
- Jack000 8y agoI think that's not a fair comparison - a digital control system needs much finer time slices to compete with human reaction time. A control system that worked off of webcam images at 4hz would be a jittery mess, or just very slow if using a Kalman filter.
- gugagore 8y agoI agree it's not a fair comparison. Your analogy, though, confuses latency and throughput.
- Jack000 8y agoyou can't do timing sensitive stuff without an RTOS, because resources could be preempted by the os or other applications. it used to be that certain chipsets could do motor control by bitbanging the parallel port, but modern pcs/phones can no longer do this due to latency.