Hi, I know loads don’t have to match between TP and intervals.icu, but my coach uses TP and I like to use intervals.icu so it would be nice if they are in the same ballpark. Also within intervals.icu “time in zone” and “HRSS/TRIMP” options are similar results for me.
For indoor cycling with power (and HR), the loads match almost identically.
But for outdoor rides with heart rate, intervals is about 1/2 TP.
My intervals.icu ATL/CTL is currently 35/37 and TP is 43/57. The difference appears to be all the outdoor (HR) rides.
Here are two recent examples of rides.
and in TP
Note both are using the same garmin recording.
Here are my zones
(note the above HR zones seem like they were auto-updated by intervalus.icu or because I was changing load options, I don’t know, but I reset the to match TP below and ran “update activities” on the setting page but loads didn’t change).
At one point my zone settings between the two were the same so I suspected the differences in the HR zones is why there is a difference in the hrTSS/HRSS … that said, I don’t know if they changed in intervals automatically or because I was playing with the different “HR Training Load” options… also my RHR is automatically updated every night via garmin, maybe that is auto adjusting intervals.icu HR zones?
But I updated my zones in intervalus.icu to match training peaks, then “updated all activities” in intervals.icu, but it didn’t update/fix any load numbers AFAICT.
Any advice on how to keep TP and intervals.icu more in line (and I’m okay manually adjusting zones a few times a year).
Hmm … HRSS only uses resting HR, threshold HR and max HR so your zones don’t matter.
Looking at the Dec 18th activity TP has load of 104 for a 1h5m activity. Load is supposed to be scaled so 1h at normalised power of your FTP is load of 100. Your average HR for that ride is only 78% of your max HR so I don’t think the load should be anywhere near 100/hour. The Intervals.icu number of 64 for 47m (moving) is 81/hour.
I think TP might be using elapsed time for the ride and Intervals.icu uses moving time. I would argue that the Intervals.icu number is better in this case.
I agree, I find the hrTSS is too high in TP. As a calibration, I’ll dual record an easy activity with power & HR on one device, and HR on another. The Intervals estimate is much closer to the TSS generated from power.
Thank you for the insights, you may be correct regarding moving time vs. elapsed time. Also, I do have my garmin setup to a non-default setting to not “pause” when stopped because I wanted to be able to automatically capture HRRc at the end of the ride or during breaks, and TP also says auto-pause is not compatible. (I verified that I am using 1/sec recording, not smart recording, turn off auto pause, include zeros for power, don’t include zeros for cadence).
I also noticed the IF is much higher in TP, for Monday / Tuesday rides the IF in TP were 0.93 and 0.73 respectively.
I also noticed that for Monday’s ride in intervals.icu the total time was 65 min, moving time 47 min, overall IF of 76%, but in the laps/intervals overview the IF appears to be similar to TP:
Also, I forgot that for my indoor power rides I’m using my garmin watch, and for my outdoor rides an Edge 1030P … although the setting are the same, I’ll try changing what I’m using to record and see if the “problem” follows the Edge 1030P indoors or the watch remains consistent outdoors between the two platforms.
Just another thank you for the insights, which pointed me to something else. Both my LTHR and MaxHR were different between intervals.icu and TP. Once I set them to be similar, the HR based loads are more comparable. My intervals.icu LTHR was probably too high (maybe because it auto updated on some ride, not sure) and my TP LTHR was too low (likely because my LTHR has increased, but I didn’t increase the LTHR).
I think between the two of those things (incorrect HR settings and that TP seems to be extrapolating the moving time intensity to the full elapsed duration) accounts for the differences (and appears to be an issue in/w TP).
