When using the Auto-Split “by distance” feature, sometimes the distances for the splits are a little less than my setting (e.g., “0.244 km” when the setting is “0.25 km”). Why does this happen?
This is due to the way the watch uses current speed and distance to predict the actual split point in your run. Occasionally the watch will over-estimate, creating a slightly longer split distance first, followed by a slightly short split. This shorter split distance allows the watch to compensate for the previous overestimation and to prevent overestimations from accumulating over the course of your activity. In the example above, the previous split should have displayed a distance value slightly longer than the Auto-Split setting of 0.25 km. This is handled this way because the GPS Speed+Distance sensor transmits information to the watch every 3.5 seconds.
Related Questions
- When using the Auto-Split "by distance" feature, sometimes the distances for the splits are a little less than my setting (e.g., "0.244 km" when the setting is "0.25 km"). Why does this happen?
- Why is CPU Vcore voltage sometimes a little bit lower than BIOS setting?
- Have an idea or new feature request for Setting Profiles app?
