Hi,
i think there is a bug when calculating GAP from intervals. On positive gradient (2.3% 0.4% 1.2%) GAP should be faster than tempo, but it shows as being slower.
Difficult to say without seeing the entire timeline. I suppose the table only has the ‘active’ intervals?
What’s happening is:
- Pace for intervals is simply calculated from interval distance and time. Second interval in your screenshot is 230m in 60sec. Thus pace for that interval is 60/230*1000 sec per km, 260sec or 4:20min.
- For GAP, each velocity point in the entire activity stream is calculated with the gap algorithm and then, those are averaged to calculate GAP for the interval. But velocity in m/s recorded by your device is already ‘smoothed’, which can cause strange results when intervals are short (like your 60s intervals).
The overall GAP from the summary looks ok to me. 6 sec faster GAP compared to Pace. There, pace is calculated from distance and moving time. GAP is the average of the entire calculated GAP stream excluding stopped time.
1 Like