jbank wrote:
Let me see if I can put the "criticism" another way. NP/TSS/CTL is a huge step forward; I've seen personally and for others that it comes as a bit of a revelation in terms of providing a metric for their cycling. The trap is that used naively, what you measure naturally becomes what you optimize, so I've seen a tendency for people (myself included) to tune their training toward higher TSS/CTL at the expense of training mix. If there is a training mix that an individual finds easier to achieve the same TSS, they will tend toward that even if it is not what would best achieve their training goal. Thus, the particulars of the measuring tool can accidentally shape the direction of training in sub-optimal ways. Addressing that shortcoming is a place where proper coaching, training plans, and/or the use of additional metrics that provide ways of measuring other dimensions of training can help add value.Wow. This generated a lot of good discussion. Anyway, I'd say this was the post that I'd most wished I'd summarized in my own original post.
In economic terms, people respond to incentives, and if you express the idea that CTL is basically proxy for "fitness," then obvious people will seek to maximize CTL.
I would say that my objection to this is really confined to triathlon. I think the concept of, especially, sTSS (swim TSS) is incredibly malformed. rTss (run TSS) is also pretty bad, though it's more/less bad depending on terrain. So in that sense, I would say that I do actually say that TrainingPeaks does, to a certain extent, guide people towards training in a certain way, and one that is not particularly well grounded in reality WHEN IT COMES TO TRIATHLON.
In that sense, I think the extension of the concept of TSS away from a strict powermeter-based concept was a mistake. And perhaps a disservice to athletes...
That said, I found the graph to be interesting. I found the discussion it generated to be even more interesting. As always, I appreciate Dr. Coggan chiming in. I have seen tremendous value in many of Dr. Coggan's cycling-related metrics. The extrapolation of those metrics - or, really, of the concept of a numerical TSS value based around a "threshold pace" value - to swimming and running, in practical every day terms, is something that I disagree with.
Anyway, did not expect to see almost 50 replies at the end of the day. Thanks to many of you for also giving me some good stuff to think about.
To continue to discuss, one thing that I've been toying with has been ignoring CTL and instead looking solely at the slope of CTL over given periods of time. The idea being that your body responds to change. So the slope of the CTL curve matters more than its absolute value. This was/is reinforced by the paper modeling injury risk as a function of ATL/CTL. A ratio of ATL/CTL of >1.5 seems to dramatically increase risk of injury. http://bjsm.bmj.com/...rts-2015-095788.full
What's interesting is that Paulo has been able to replicate these findings with his athletes, only Paulo uses longitudinal RPE tracking (with a separate constant for each sport). So he tracks A*RPE*duration where A is a constant that varies by sport. And that gives him a training load score for that workout. He then tracks that over time, using some basic math - similar, I believe, to Dr. Coggan - to represent ATL as roughly 7-day load and CTL to be 6 weeks plus.
I'd say that looking for a slight - but positive - slope to your CTL curve is more important than the actual value of CTL. I think that's the sort of thing that TrainingPeaks could offer more of and that might encourage more intelligent training.
I haven't yet played with it, but given that I've found value in the derivative of CTL - slope, I'm not curious if you could look at "fitness" (loaded term) by examining the area under the CTL curve - the integral of CTL - over varying periods of time.
"Non est ad astra mollis e terris via." - Seneca | rappstar.com | FB - Rappstar Racing | IG - @jordanrapp