I suppose because as we know FTP is not a number but a range ![]()
Iâm stuffed if I know the correct definition of FTP. Everyone seems to have their own interpretation on the original term.
No matter which way you try to determine the number it will be dynamic.
I really hope TR come up with a way to blend the ramp with something better than 1m max power.
Garmin, Xert (on the Garmin) and intervals icu seemed to have no problem providing a decent estimate from my recent ramp tests.
I had to find my last ramp test and apparently intervals.icu estimated it from last 6:30 min. It was done the day after KM test to test the difference between tests. TR last min FTP was 10w lower than my real FTP and intervals.icu estimation was 1w higher so spot on. So at this particular moment the multiplier in TR should be 0.77 for me. But the ramp test is basically random numbers generator in my eyes ![]()
A lot of people are saying that Xert, icu etc will underestimate etc because youâre following plans which donât push you to that level.
Surely you are all training for some kind of event, or do bunch rides which put you on the limit to give you some data ?
Of course power based estimates need good data to give a good estimate.
For anyone doing structured training + a decent amount of racing, xert intervals.icu should be pretty close. Mine is normally not far off a test.
Racing is the key part in this equation. So you are doing some efforts close to maximal. It is not important where they come from. The only point of training is to get better. To check if you become better - the maximal efforts are needed and then there is a bunch of software that estimates your FTP pretty close to actual value.
I think thatâs the problem for a lot of people. They arenât racing, or they donât ride hard outside very often.
Maybe Iâm misremembering but I feel like Nate mentioned wanting to do away with ramp tests in the future? I would think TR has enough data that they could pretty accurately predict what the next ramp test based on current performance.
A number dont raceâŚthere was a thread on this some time ago.
Depending on how you ride and what efforts you are doing you may not actually push your limits or your power to trigger even a bump in FTP based on the modeling done by say Xert or Intervals.icu.
My group rides are not hard rides. So I can do a couple of SSB rides and a group ride in a week and rarely go above my FTP. Rides may be long in duration but not result in a sustainable effort above FTP that would necessarily model a bump in FTP.
My own riding this year had such a period. Intervals.icu had me declining in FTP. Lots of long rides. Good effort but steady and not over FTP. You could track the changes in my heart rate and power and see the improvement. It wasnt until I did an FTP test that intervals.icu showed the increase which was above previous FTP. The models are reactive to how hard we ride. They do not project what our FTP will be based on are riding.
Iâm on the same page there. Itâs not really a problem as such. Unless youâre expecting an accurate number from one of the many estimates available.
I can imagine the peeps doing traditional style HV base plans fall into this category. Even SSB1 struggles to get good results with Xert and the like.
You can change your âdecay rateâ in xert to âNo Decayâ if you are planning on a long period such as early season base with no max efforts. This will still provide you with increases in TP and LTP as your training load progresses but with prevent the big decreases that you might see with no max efforts.
From xertâs manual:
When you change the Signature Decay Method to No Decay â Training Load Matched , the system does a number of calculations to help you better manage your signature during times where you havenât done or donât plan to do any breakthrough efforts. (In control systems theory, we would say that the system is going through a period of dead reckoning ).
Under the covers, Xert establishes the relationship between your training loads and your fitness signature parameters. When you have robust historical data, without large gaps without power data and without power meter errors / changes, Xert matches your historical breakthroughs with individual training loads.
And in my experience it really works.
Nate has also mentioned and hinted at adaptive plans and big data / machine learning / AI.
One way to close the loop on the result of a planâs effectiveness is to use the ramp testâs estimate of 5-min vo2max / aerobic capacity (its the last 1-min power from the ramp test).
The current plans donât include max efforts, except for the ramp test, so if you are only doing inside workouts then âcurrent performanceâ can only be estimated by ramp test.
I would guess that FTP tests will soon be things of the past. This problem seems very amenable to machine learning/statistical modeling, and all of the major players have enough data to train models. Intervals.icu is pretty close already. Iâd wager that before long you wonât need an all-out effort to get an estimate thatâs within 5% of true FTP.
If any of the big players were to open source anonymized data, thereâd likely be a model available within a few weeks. Meantime, we have to wait for TR to hire an ML engineer ![]()
But without non-workout rides, Xert will constantly decrease your FTP. That is, if you studiously followed a TR sweet spot plan, then Xert would say your FTP is going down.
There is no way to estimate FTP without efforts that essentially âexpressâ your new fitness. Which is essentially what the ramp test is
I had a very different experience with Xert: without constant break-through / really hard rides, if I just trained, Xert would constantly decrease my FTP. This is why I dropped Xert (for the 2nd time): for me, I couldnât use it to âeliminateâ FTP tests / use its âmachine learningâ to inform my training
I think any model is going to need efforts to calculate off. Even if TR got rid of the ramp test, the system would still need to prompt the rider for a 1, 3, 5, 10, 20 minute or whatever max efforts every now and then so it could calculate FTP.
I have considered looking at HR along with power to try figure out what the max version of a given sub-maximal effort might look like. That could work but HR varies a lot so would give quite a wide range of results. So I decided just to stick with max efforts for now.
I can get a pretty good idea myself of where my FTP is just by watching how my HR rises on a 14 min climb near my house, without having to go full gas.
Maybe, but Iâm guessing that having features like âHR as a percentage of maxâ, RPE, HR minus resting HR (perhaps divided by wattage), diff in HR divided by diff in watts, etc. would get us most of the way there. Even max efforts arenât guaranteed to be max efforts (people have bad days, some people are able to push themselves closer to their limit, training fatigue plays a role, etc.), so itâs possible that a model might even be better than an FTP test for some riders on some days.
You obviously didnât select âno decayâ for your fitness signature
Yeah, I think youâd want to throw a bunch of selected features at a model that predicts reported FTPs, using only data that are collected within a short time window of the FTP test. I could be wrong, but I suspect that such a model would perform fairly well. Would love to get my hands on some data â and some time on my hands â to try!