This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Pace wrongly calculated!

I am totally frustrated by the pace calculation in my FR255. It must have some implementation errors with round offs.

Situation:
I am a European (half) Marathon runner-> pace in km / min and able to keep a constant pace here where it is really flat.
I follow the Training suggestion long run 16,1km  5:36 - 5:18 min/km. (that is already a minor frustration as these values are only derived from imperial).
And I have an autolap set at 500m, so I do get regular feedback on my pace that I can calcualte myself.

And at around Pace 5:30 I can exactly keep running in Heart Rate zone 2. So I try running with an actual pace of 5:25 - 5:35, mostly towards the slower border.

Now for vast amounts of distance, my FR is calling the 'too slow' alarm. But with pace 5:35! Easily 50 to 60 times during the 1,5 hours run.
Strange. The Coach function had the workout thresholds set on 5:36 - 5:18. So the pace is OK but I am too slow?
As pace is a rounded figure, it could be that for a really long time, I am just doing 5:37. But I hardly see Too Slow 5:40, mostly Too Slow 5:35. In itself this is pretty frustrating.

But where the watch confimrs the pace must be wrong is every lap time. Mostly my laps are betwen 2:42 and 2:45. So a pace of 5:24 to 5:30.
How on earth can that be?

My actual pace show mostly 5:30 or less. My watch is beeping I am too slow at 5:35. And then confimring I was running the last 500m at 5:25.

I have a suspicion  there is a lot of rounding being done calcualting the pace. Perhaps from Imperial to metric.taking the average over some seconds and then more when comparing that average to the workout borders.

  • I have also noticed that the watch is really slow to update the pace (shown on display at real time) when speeding up/slowing down. Which is really frustrating during some workouts. 

  • Indeed. This is where I think steps with round-off lead to my frustration.
    5:36 / km is 540,74 seconds per mile.

    Probably the border of the training lies at 540 seconds, leading to 335.5404 seconds = 5:35, 54. So the border probably rounds up.
    When now the pace over some 10 seconds comes to 5:35,6 then I would be too slow. With the display showing 5:35 TOO SLOW ?!?

    I would need to be able to set the pace border at 5:37,5, and then have at least the speed comparison OK, as then the notification would be 5:40 too slow.

    But why there is quite such a difference to the pace when comparing to Lap Time.
    In itself that is no too bad. It results in slightly underestimating the pace, or perhaps an optimistic distance measurement. That is OK, because there is nothing so frustrating as finishing a HM, and then not having a personal best because the watch only measured 21,0km. There 21,2km definitely is better.