Ok, thanks - yes you'd expect a few duplicates just because there's always a chance the value really will be the same two times in a row.
So on yours, even with the old algorithm it was still out? Because I could imagine the new algorithm might be expecting the time difference between samples to stay constant rather than varying slightly per sample, and that might throw it off - but the old one should have been fine
I could imagine the new algorithm might be expecting the time difference between samples to stay constant rather than varying slightly per sample, and that might throw it off
And from the log I attached you see this is the case? You see it is better on newer watches?
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
Ok, thanks - yes you'd expect a few duplicates just because there's always a chance the value really will be the same two times in a row.
So on yours, even with the old algorithm it was still out? Because I could imagine the new algorithm might be expecting the time difference between samples to stay constant rather than varying slightly per sample, and that might throw it off - but the old one should have been fine