3 ms·
If you try to "predict the present" based on the past (and when you use previous points to calculate velocity and acceleration, that's what you're doing) it wil
by skybrian 7y ago
If you try to "predict the present" based on the past (and when you use previous points to calculate velocity and acceleration, that's what you're doing) it will overshoot when there's a change in direction, and how much depends on how aggressively you try to extrapolate. For the one-dimensional case in signal processing, doing this with a quickly-changing signal like a square wave will result in ringing.
It can smooth things a bit but it's not that good a substitute for actually improving latency.
(There are probably consequences for coronavirus charts as well, since they're based on lagging data.)
- xellisx 7y agoComment almost sounds like it's about PID.
- modeless 7y agoAlthough I agree that there's no substitute for actually improving latency, I think it's possible to do significantly better at prediction. Mouse movements are not easily predictable but they are also not completely random; this is a good type of problem to apply machine learning to. Ultimately you want the lowest possible latency and prediction, because you can never get the latency to zero. Once the latency is small enough, prediction becomes a net win. For example, all VR devices do prediction for head and hand positions after lowering latency as much as possible elsewhere.
- Rauchg 7y agoI totally agree, you want both. Negative latency! https://rauchg.com/2014/7-principles-of-rich-web-applications#predict-behavior https://rauchg.com/2014/7-principles-of-rich-web-application...
- fiddlerwoaroof 7y agoThat demo looks like the sort of attempt to be helpful that really irritates me on web sites.
- MauranKilom 7y agoI would reckon that overshoot (the mouse cursor moving "backwards" after over-prediction) is significantly worse than undershoot in terms of user experience. We can easily compensate for mouse acceleration not being constant (ask anyone with enhanced pointer speed). But the pointer doing qualitatively different movements than what you input is annoying. In the limit I guess this boils down to "do no prediction" (which I also suppose is what the linked site's conclusion is).
- deleted 7y ago[deleted]
- benibela 7y agoReminds me of a Kalman filter