I’m following a tri plan for duathlon training ( so take out the swims) but I’ve noticed that the calendar/ weeks plan only has tss on the cycling activities and not the runs?? How does this work for adaptions if it’s not taking them into account.
You have to manually put the run TSS in after completing the run or select an intensity and it will calculate it for you.
Runs dont get adapted as far as I know. Just a static part of the plan.
1 Like
TSS is a cycling-specific metric. It does not apply to other activities.
1 Like
Ahh I see, so how is training stress on the body from running measured in TR and so considered in the overall plan obviously taking into account muscle fatigue?
Please explain this a little further. as there is a TSS given for prescribed runs on TR triathlon plans.
Not who you were replying to, but he’s correct that TSS is a cycling specific metric. “TSS” estimations for other sports or not based off power, are at least somewhat different than cycling TSS. They just use the same word because of people’s familiarity with it, even though they’re actually different.
I’m not quite sure how TR estimates a “rough TSS equivalent” for non-cycling activities. I’m not sure if they’ve actually shared that publicly. My best guess is that’s it’s using their “estimated TSS” that’s based off RPE:
Regardless, be aware that attempts to invent imprecise training metrics, and then combine them with training metrics for other sports that are measured differently, are going to give you a number… but what that number means exactly is a bit of a mystery.
It’s like you put some pork, a dead raccoon, a boot, and a tablespoon of material from a neutron star into a sausage maker, and declared that the resulting nuclear explosion is in fact a hot dog. I mean, you’ve certainly made something. I’m just not sure that putting ketchup on it and taking a bite is a particularly wise decision.
More seriously, it’s telling you something I guess, just not very precisely. And without certainty on what it’s telling you either. And you might be better served by paying attention to other metrics (volume, how you feel, etc), rather than just a pseudo-objective number.
3 Likes
I’d eat that, as long as there was mustard on it.
Thanks for the recipe👍
1 Like
Agree. Put mustard on anything and I’ll usually eat it.
1 Like
1 Like
Yeah, it’s probably not unreasonable to give you a ballpark estimate of what’s going on. I would just be careful about ignoring other pieces of info, or putting too much weight on it alone.
What’s there to explain? As I stated, I developed TSS as a cycling-specific, power-based metric. It doesn’t apply to other sports, nor can you calculate it from HR* or pace.
*Although if you’re using my PMC, you may - or may not - wish to estimate it occasionally from HR, as described in paragraph 2b of “Applying the Performance Manager concept” here:
(Note: my words begin with “Knowledge of…”.)
3 Likes
Now that’s funny!
Recipes aside … I’m not sure I get it 
. I understand that tr uses perceived effort on runs to create a ‘tss’ type figure, but my question and concern is , is any number ( however roughly estimated) being taken into consideration for the overall training week if you are doing the tri plan ? And so being used in adaptions ?
I’ve noticed runs don’t get adapted, but does this mean runs are not being taken into consideration overall in the training week ? And if not, what is the point of following a tri plan if it’s inaccurate?
1 Like
Easy, big fella. I’m not disagreeing with you. Just curious as to why TSS is assigned to run workouts on TR. someone else already explained, and they did it politely.
You’re safe on your throne of TSS.
2 Likes
A 30min run gives 77 TSS, a 41min run 106 TSS…looks strange to me…?
Not for me. A 35 min run ( easy) is only 25 tss
Agreed
If we ignore that TSS wasn’t designed for anything but cycling, the numbers used for the estimates in your TP screenshot seem wildly high. For example, in your pic, a 30 minute run is showing 77 TSS.
I understand why you want to do this, but I think you need to shift those numbers down significantly.