Might it take the distance covered earlier into account when calculating pace?
Did the distance and duration shown in the UI start from 0? As far as I can tell the pace comes from exactly those values, so I guess one of them must be off.
I did notice that without the kalman filter code, the reported distance does seem to be a bit higher than I remember it being before - so that could be it.
The problem I have is I'm receiving conflicting reports! I had someone earlier tell me that what seemed to be the uncorrected distance calculated from the GPS trace matched up exactly with an Apple watch, so I thought I'd just use that. But it seems that maybe the GPS trace does need some kind of filtering now (or maybe altitude shouldn't be taken into account since that does fluctuate a lot due to GPS being less accurate for height).
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.
Did the distance and duration shown in the UI start from 0? As far as I can tell the pace comes from exactly those values, so I guess one of them must be off.
I did notice that without the kalman filter code, the reported distance does seem to be a bit higher than I remember it being before - so that could be it.
The problem I have is I'm receiving conflicting reports! I had someone earlier tell me that what seemed to be the uncorrected distance calculated from the GPS trace matched up exactly with an Apple watch, so I thought I'd just use that. But it seems that maybe the GPS trace does need some kind of filtering now (or maybe altitude shouldn't be taken into account since that does fluctuate a lot due to GPS being less accurate for height).