Right now I come out the solution for pace:
1. Calculate the distance (d1) for first 3min (To get reliable value about distance)
2. Get pace=d1/3min;
3. Shift 3sec to get the distance (d2) for full 3min;
4. Get pace=d2/3min;
So, that means, we will have a value for pace, updated every 3 sec.
And it will show the average pace of the last 3min ? Of course displayed as Km/Min. ?
From my point of view, this will improve the current solution. So it's okay to have it !
On the other hand... (I'm sorry, there is always an "on the other hand"...)
... I think, that 3Min. might be too long for some situations:
For speed training I sometimes run short distances like 200m (< 50 sec.)
or 400m (< 100 sec.) and it would be nice to get a feeling of pace for those
distances too. And as you can easily see, here 3Min. are too long !
I know, that a longer distance makes the pace value more reliable.
But a shorter time applies more to the basic idea of current
Basicly we want to see the pace of this moment
, not of the last 3min.
So, we have to find a compromise of these two requirements.
And 3min. are not so bad... But what about 2Min. ? Or 1Min. ?
You know: My favorite solution would be a configurable value, so that users can
decide what they consider to be more important.
However - what ever you want to implement: It will be better than what we have now.
Pace1K keep 1 full km to calculate.
Sorry - but after the long and detailed discussion about this subject,
this statement was a little bit to short for me.
I do not understand, what you want to do here
Best regards, Hubert