If I was TR, I would stop referring to FTP almost completely, and definitely stop equating anything to do with ramp tests to FTP and/or a rolling fitness assessment for consistent TR subscribers. FTP is a hugely confusing and arguable concept, and listening to TR folks talk, they definitely seem to have their own definition of it compared to others.
Everyone should Google “FTP” vs “LT” vs “MLSS” vs “CP”. It’s a super deep rabbit hole and I haven’t found any light at the end of the tunnel.
It seems to me that what we are really after is proper training zones. Reading the literature, I have yet to find a singular magic number. So why are we trying to identify one or even talk like there is one? Aggregating everything, what we are really talking about is identifying and working in a “threshold” zone: e.g., power range where one can do repeatable efforts from 8-30 min with ~5min or less rest intervals. Identify that zone, and you have a great basis for setting up everything else. And a ramp test is an easy way to get people near that zone. So are other metrics, like doing 10 and 20min repeat workouts. Or a 20 min max effort. Or a 30min max effort. Etc. Each assessment will yield different numbers, but they will all fall around a threshold point where TTE rapidly drops off at higher intensity and rapidly grows at lower intensity. Where a person should train in that zone comes from experience level and racing/fitness goals. And once you have an initial guess, it is easy to refine it while training by doing weekly efforts that are hard.
The problem only comes in when we try to pin down some singular number that no one agrees on what that singular number means. We’d make a lot more progress in debates on proper training intensities/recovery and also in assessing fitness if we dropped trying to chase a unicorn.
Good points. I know and understand ML, but that was not my point. It was about not going all out and deriving conclusions from that data. I guess you summed up my conclusion:
If you don’t go all out, your training zones will be less precise (and therefore possibly less effective)
with:
Will that ever work as well for people who push less hard? No, it cant, but then again the act of pushing hard is half the battle so why would you expect it to.
I seem to recall they switched to 2W/kg. Pretty sure when I first started on TR the default was 200W so you needed to do a couple of tests to hone in on a reasonable value (notice I didn’t say “accurate” ), that took a while with the 8min and 20min tests.
Your FTP changes tend to be asymptotic, i.e. large beginner gains slowly levelling off to a steady value. You are unlikely to see a series like: 200 - 202 - 200 - … - 200 - 250 for example. So actual testing in the early stages of training (or when switching from another training program or changing kit) makes a lot of sense. After a year or two it’s less likely to vary and most will have a good idea whether it’s accurate/appropriate so an estimation is probably good enough unless you have a desire to be more precise. My FTP is 288W, if I took a test (Ramp or otherwise) and got a value of 289W, other than confirmation that on that day my FTP was reasonably accurate I haven’t gained anything.
Personally I’d be better concentrating on my short power, truly pathetic is one way to describe it! Here’s my intervals.icu chart of my age adjusted percentile ratings. (Edit: the brown line is current “season”)
You end up comparing a “one of” with a “one of” which doesn’t make much sense.
My FTP tests so far in Trainerroad using the ramp test:
311, 303, 326, 333, 346
These were taken over a 6 month period to last week. I compare them as a set as opposed to 'one off’s and can see a clear trend that holds value for me because I feel confident that I’m doing the right things.
My point exactly, one value is useless, 2 are kind of valid if ± the same, 3 start a patern, etc… That’s why regular all-out/testing is useful in my opinion. It actually takes into account environmental variables, I welcome them instead of try to get to the theoretical max of my performance. It gives perspective and therefore I’m in a better position to asses my situation.
Actually, it helped me foresee a burnout in the past. In this case of the 303 value, I was a bit sick in retrospect.
Thats what Intervals.icu’s eFTP is good for (my app). You can go out to do a 20m max effort and if you still have gas in the tank (and haven’t run out of hill) just keep going as long as you can and you will get a better number. Likewise if you blow up at 18m you will still get a good number and won’t have wasted the effort.
If you are out and about and feeling good you can just smash whatever hill comes next and see what you get. Doesn’t matter if that only takes 12m.
What is this claim based on? You’re guessing. My Ramp Test FTP has always been BS, despite it being a max effort. There are ways of estimating FTP without a max effort, such as heart rate drift at different intensities and durations or the RPE / compliance combo with a set of over-unders.
On your point of estimating FTP, what accuracy do you think will be achievable? Can you post a %HR vs Power chart for a set, of say 50 intervals?
I personally find HR to be a very unreliable metric. That seems to be the opinion of many others too, hence the popularity of power meters and the reliance upon them for training and/or training result analysis.
Intervals.icu estimates you FTP based on peak performances. For me, it is 1 (!) Watt of my real FTP. So i think it should be no big deal to estimate an FTP instead of doing specific tests
Slight tangent, where is this dispalyed? I’ve just been looking through the beta app and website but can’t see a toggle? Or is it just a coming soon internal feature at the moment?
It’s a long term aim/goal, I think it was mentioned on the original podcast about AT as well as the one from a week or so ago. Some people took that to mean it was available, etc. It may be a feature available only to TR staff but beyond that it’s just vapourware ATM.
My intervals.ice eFTP is only within a watt or 2 within days of my ramp testing (obviously, this makes sense). But with base training it tends to decay over time because I am rarely doing any effort over 104% FTP. However when I re-tested my ramp it increased 4% from my first ramp test before SSBLV1. So the issue with the estimate on their website (and potentially TRs estimate) is that if you don’t have any suprathreshold data it might bring your eFTP too low?
If I had changed my TR FTP to the intervals.icu one continuously I would have shortchanged myself at the end, training at levels too low for myself (which AT could have changed, but that takes time…). I think it is a complex problem - but the thing TR has going for it is the amount of data they have looking at specific workouts, tests, and FTP data.
You do need to do a max effort every now and then to keep eFTP up to date. I might change the decay formula at some point. At the moment if you reduce training load it decays slowly. Would perhaps be better to decay only if you haven’t set a new eFTP in the last 6 or 12 weeks or something.
As someone whose motivation for max efforts rarely coincides with test day I am very much up for a system that just lets me get on with bike riding.
It’s also worth remembering that FTP isn’t some kind of physiological marker - it’s an (often very good) estimate of a level to base your training on. As such, having different ways to reach (20min tests, ramp tests, roboChad) and implement (AT, 4DP, etc) that estimate just gives us a bettet chance of choosing something that fits.
I must admit that it was so close just on the day I wrote my reply. Today we are already further apart again. Tonight is a FTP test on the program, then TR and Intervals.icu show the same again anyway.
I don’t think TR is going to be estimating FTP based purely on max efforts in any case.
What I was getting from Nate’s comments was that it is going to be analysis-based, using your personal training history and the FTP gains their ML model expects to see from that. I.e., predictive rather than analytical.
It is basically power output @ MLSS (maximal lactate steady state) and more convenient for people to test / estimate than to determine MLSS via ramp test with blood lactate measuring devices and then estimate / calculate FTP from the blood lactate / power curve recorded during the test.