I’ve tried HR and rTSS. As a cyclist who runs off season, the wear on the legs is just more aligned with rTSS. However, the over estimate most see in TSS for rTSS versus HR is just a little much here.
So question is, if I set my run threshold at something I’ve not even ever done for a full hour to try to tamp down the rTSS over estimate…why is it still giving me values at a rate of 118 TSS/hr which would be way over threshold?
The pace set for threshold was 07:20. I ran 48min at like 07:53, gap was only 07:48. There’s a little hill in there, but nothing noteworthy at all to really account for such a wild over estimate.
I would go with HR TSS, but my bike fitness depresses that value SO much it’s worthless to express stress in training per week. If I were a runner only, surely I’d do HR instead.
Suggestions? Set the threshold even faster even though I’ve never done an hour that fast? 07:20 would be a stretch already for an hour. My mental math here would seem I’d need sub 7min/mi to make the numbers be closer. Which isn’t possible in reality for me to do. I could try, but seriously doubt I could.
Is your HR set differently for running and cycling? My threshold HR for running is 10-15 bpm higher than cycling. This would explain why you’re so far over TP’s threshold rate for running.
I would go with HR TSS, but my bike fitness depresses that value SO much it’s worthless to express stress in training per week.** If I were a runner only, surely I’d do HR instead. **
Nope…all pace, all day, every day.
I’ve been a pure runner for the last 3 (ish?) years, and I all but ignore HR when running. Pace, RPE, and cross-check against HR when its hot.
When I Google’d setting the pace in TP, for some reason the link I used said “hour” pace. Which for me is a lot slower than 5k pace. As I don’t run half marathons and such.
I appreciate it. I think that will definitely bring it into check. And a 5k test is manageable for me.
Same pace, similar result today on 5mi run at lunch. 08:23 pace, within z2 of the Friel zones on TP for a 07:20 threshold. Still gave me 76 TSS for a 43min run. That’s over 100 TSS/hr in zone 2.
I have submitted a ticket to Trainingpeaks as none of the literature seems to address the math of awarding rTSS by pace.
So I changed this at the time of this topic based on this advice, and it did help.
A question remains: Why does it still reward rTSS at a rate equal to 100 TSS/hr when the run’s pace was under threshold by a whole minute per mile?
Threshold set at 7:20, lunch run at 8:40. Awarded 52 TSS for 32min of work. That seems too generous still for being a whole 1:20/mi slower.
I think I read somewhere that if you ride an hour at threshold power you’ll get 100 TSS, but if you run an hour at threshold pace you’ll get 120 rTSS.
It is designed this way since running is more taxing on the body or something like that.
Sorry, don’t remember where I read it.
So I changed this at the time of this topic based on this advice, and it did help.
A question remains: Why does it still reward rTSS at a rate equal to 100 TSS/hr when the run’s pace was under threshold by a whole minute per mile?
Threshold set at 7:20, lunch run at 8:40. Awarded 52 TSS for 32min of work. That seems too generous still for being a whole 1:20/mi slower.
I think I read somewhere that if you ride an hour at threshold power you’ll get 100 TSS, but if you run an hour at threshold pace you’ll get 120 rTSS.
It is designed this way since running is more taxing on the body or something like that.
Sorry, don’t remember where I read it.
Ohhh. If so that would make total sense what I am seeing. And would match perfect.
Test could be me go run 10min at exact threshold for an activity and multiply by 6 to see if I get 120.
In app I had set the new threshold but did not apply the zones and save. So it saw my new threshold to display it but the zones were from old slower setting. So when it calc’d, it used the old zones.