Gradient adjusted pace + Pace training load

Intervals.icu now has gradient adjusted pace for running using the same model Strava uses. You can configure running to use GAP for training load. There are also pace zones but no “time in pace zones” yet. You can control the default training load priority per sport.

Question: Should “time in pace” zones use GAP or normal pace?

Runs with GAP have it displayed in the summary. You need to re-analyze or re-apply zones to get this on old activities.

The edit training load dialog shows all load values:

I am going to add GAP to interval stats.

7 Likes

Woohoo! This changes some things :smiley:

Wow. Thats a pretty extreme example!

It’s hard to say which formula is right :slight_smile:

If possible make it user selectable?!

Reasoning: For users with power data that mostly takes care of profile/gradient. For users without it might be more useful to use GAP. The problem I see with GAP is the quality of elevation data (imho both sources altimetric and taken from map data are not totally reliable).

1 Like

If you have power data then that will be used for time in zones. I will need to make use of GAP data for load and time in zones configurable or perhaps auto-selected depending on the data. Strava do a good job of cleaning up the gradient data. I need to try do the same.

Great news, thank you :blush:

I can imagine this is tricky, also depending on the data source. Altimetry needs to deal with hysteresis, so there is probably some integration being done, and thus a time delay as it’s written to the fit file. Probably not all companies use the same algorithm.
If the source is map data, quality depends on region, GPS position…
So I can imagine different data sources need different treatment.
It also looks to me that Strava does a good job of cleaning up that data. So what ever they are doing, it seems to work.

Different companies use different algorithms. One of the biggest influences on altitude charts (from barometric pressure sensors) between different brands is the minimum delta used to count as an altitude change. Some use 3m, others use 5m or even more. I think they choose a value that matches best their typical pressure sensor. Most units do agree quite well if you do longer climbs. Differences are much bigger on rolling terrain. 30% difference in altitude gain is not uncommon. If your sensor fluctuates right above the minimum delta accepted, the unit is counting loads of faulty altitude gain.
Environmental barometric pressure change can be adjusted for when doing a round-trip because you know that start and end altitude are the same. So you can correct with a linear offset and be pretty close to reality. If not a round-trip you could take known altitude from start and end points from a map and use those to calibrate your pressure sensor.
There was a SportTracks plugin once that did these corrections quite well.

When do you plan to implement PACE based workout building?

As soon as I can. I have a bit of a bug backlog to clear then will be on it (need to sort out issues with GAP on flat runs etc.). So I the next week or so likely.

1 Like