They eliminated the free workouts and tests a few months ago. You can still do it during the 10-day free-trial period without having to provide payment info.
1 Like
Thanks @Slowwithouttwitch. If I ever need a more accurate FTP measure, I may give this a try. Such precision is beyond my current needs.
My point, though, was not that AI can somehow correct for a badly measured FTP to create an accurate one.
Rather, I’m saying that there’s no advantage to giving TR a “better” FTP metric. That will not result in a better training plan recommendation for most users. Why? Because TR is statistically optimised to convert ramp test FTP (or AI predictions of ramp test FTP) into the most beneficial workouts. You might actually expect TR to make worse recommendations on average if you provide a “better” FTP. They didn’t have that data when they created the model, so they can’t necessarily use it as input to the model prediction.
1 Like
How should that work while people get unpredictable results from a ramp test randomly on either side of their true FTP?
What you maybe refer to is the adaptability of the workout difficulty prescriptions to accommodate for a wrongly estimated FTP. While that for sure works for millder offsets, the forum is full of people in trouble before any adaption had a chance to fully kick in, especially the population where the ramp tests rather severely overestimates their FTP.
Ok, I have no dog in any fight here, but happy to outline my understanding. My professional background has overlap with this kind of thing (like other users here), and if that helps I’m happy to chime in, openly admitting that I have no “inside track”, and could be quite wrong.
All measurements (of anything) have random variations on either side of the supposed true value (often expressed as a “confidence interval”). FTP measurement no different. FTP is even harder, because it’s not a directly measured quantity, but rather inferred from some proxy measurements (such as a ramp, or 40min test).
TR’s recommendation model accounts for this by the fact that they have many measurements in their dataset, and many workouts and resulting gains that they can fit their model to.
The resulting model is the best statistical fit for the data of many users, and predicts what workouts would, on average, benefit a subgroup of users with similar parameters (“Ramp FTP”, “PLs”, age, …) to the user being evaluated.
However, the user being evaluated may differ (in workout performance, or resulting gains) from the average user in that subgroup. Then, the difference between their observed performance and the anticipated performance can be used to predict such discrepancies in future for that user, compared to the subgroup.
I don’t believe TR is trying to accommodate “wrongly estimated FTP” using adaptations. I think TR doesn’t really care about “real FTP” at all. They care about making good recommendations based on the available data. And the available data is Ramp-test “FTP” (plus other parameters like PLs, and observed performance data). So when you provide TR with input parameters for prediction, they should be the same ones TR used to construct their model, imperfect as they may be. Those will deliver get the best predictions from the model, and will minimise the amount of “correction” required, on average.
Some unlucky users will initially get poor recommendations, because they happen to fall in a particularly poorly represented subgroup. They have two options:
- Wait for (and work with) the adaptations system to do it’s thing, while it tunes for their specific case, based on their feedback, and their performance data.
- Manually change their TR (Ramp) FTP input parameter to whatever value they think will deliver more suitable results. Note: the optimal value (the one resulting in optimal gains) is probably not your “true FTP”, and choosing the optimal value is not easy.
I’d recommend option 1, with help from TR support as needed, but if you’re having great success with option 2, obviously keep doing what you’re doing, and kudos!
6 Likes
I can’t add anything profound here. Others have made amazing suggestions. But, I understand your plight. At 58 I have to prioritize sleep. I need it for recovery more than ever. Interval and strength work days knock me out. I love doing them but if I get 1-2 bad nights of sleep I start feeling awful and everything suffers.
I also fuel a lot and probably over eat on the bike. I kinda of like doing it. Depending on the day, I’ll eat a ton of oats or some carbs-based thing before a ride.
The only other thing might be tweaking your training. We don’t all respond the same way to the same stuff. Whatever you land on, just be consistent.
Good luck!
1 Like
WRT to the Wahoo Systm FTP test, I like to advocate doing their 1 week test prep plan. It includes two days of warmup, their “Half Monty” ramp test on day three, a day off, two days of warmup, and their “Full Frontal” 20 minute test. The HM results are used to suggest power to maintain for the FF test. In the FF, I try to just beat the suggested power levels and it’s killer. IMO, it provides a very consistent lead-in to the final test, and is a very solid week of work as well.
2 Likes
Even a solid 25-35 minute effort will get one in the ballpark. I just did my first FTP test of the year (KM stytle). I knew what my FTP was by minute 25. I carried through to 35 minutes and stopped. I could have struggled to do another 5 or 10 minutes but there was not point because I had felt out my FTP and TTE.
I think that’s BS. It may work on statistical averages but it will work better with an ftp that is bang on accurate. Otherwise, you have to go through a period of workouts that are too hard or too easy and wait for the system to adjust. If they are too hard, you might burnout during the adjustment period. That will probably lead to more time off the bike to recover. It makes no sense to go through any rounds of that.
Just go do a real test and get your training on track immediately. A simple way is to just ride 30 minutes at the current FTP. That should feel like a 7 or 8 out of 10 effort. If it is a struggle FTP is too high. Lower power during the effort until you find the edge of a long sustainable effort.
TR works well within its bounds; it tests, it analyses, it responds to user feedback, it adapts. FTP has never been less important, it’s just a training number now, one that fluctuates, you don’t need to argue any more or bend over backwards to find “truth”. It couldn’t matter less. The important thing is getting the right, consistent progressive overload training …over time.
Id bet that if I added or subtracted 50 to my FTP the system would rectify itself in a few workouts.
4 Likes
Hard agree, but that’s assuming a well-calibrated RPE. My assumption was a moderately-calibrated RPE in order to be on the safe side. 
1 Like
sure_jan.gif 
2 Likes
Everyone thinks they are at the edges of the bell curve, the reality is that almost everyone reading these posts, if not contributing to this very thread, are slap bang in the middle and absolutely covered by the rules that apply to most of humanity.
Search gluten intolerance, good drivers, and human intelligence for more.
3 Likes
I’m not sure that I follow the logic?
The app has a test, and AI analysis to create an anchor number for training. They analyse millions of these tests and analyse the performance in the consequent workouts, and refine accordingly.
Why would any manually set number work better with this system for any particular cohort? And how can you objectively know which cohort you are in?
Then, given the PLs adjust immediately after the first workout and feedback, what is the priority on manually ‘fixing‘ FTP whatever cohort you think you are in?
Thats all fine and good (I would almost say that its too much…)
But the question is what you eat before the ride. Carbs on the bike doesnt matter if you come in with low glycogen in muscles and liver.
If you felt like the first sessions felt fine, then as the plan progressed it felt harder and harder, I would bet that you don’t eat enough off the bike, don’t recover properly, and then try to make up for it with 100g/hr on the bike (which won’t work long term).
2 Likes
the issue, esp with TR, is a bad FTP estimate has a cascading effect, and progression levels are no panacea. I’ll contend that ilevels with wko gets athlete differences better, particularly in an area like vo2 work, where someone like me does vo2 work in the 110-115% area for 4min intervals, whereas someone like one of my athletes does 130% for similar intervals. TR, even with progression levels, are so beholden to %FTP that having that messed up just makes things worse
2 Likes
And yet someone like the OP is struggling the training. He’s not on the curve detected by the AI.
I’m glad you are here to be the defender of the AI. 
Because, clearly, one can do a better long-form test that doesn’t involve short efforts above threshold.
1 Like
The fact the TR has to run adaptations immediately after an “ftp” test (they still call the ramp teat an ftp test, it was never designed for that because of the obvious issues with using efforts >FTP to determine FTP) shows that it is not terribly accurate.
You can skip the whole adjust workouts until you are in the right ballpark of your FTP by just doing a proper test in the first place.
This saves you time, stops you from doing workouts that are not optimal and gives you a number you can be confident in from day one.
3 Likes
A great explanation. 
1 Like
I can easily get a ramp test result which I can’t hold for 20min straight later.
Before anything adapts you get demotivated, sick and burned out.
If your test result is on the lower side I can see where what you describe might work.
At least if people don’t give up for other reasons, like being afraid of loosing fitness.
1 Like
I think every athlete figures this out by paying attention to how they perform relative to “FTP” in workouts of different kinds - eg threshold, VO2max, anaerobic, etc.
Even before I started cycling, I knew I skewed fast twitch / anaerobic. This was validated once I started riding with a power meter. For example, my most recent TR workout was a 9.6 PL anaerobic workout. And I could have done harder. But I can just about hold 90% of my “FTP” (ramp test minus 5% for me) for 60 mins - which according to TR is a sweet spot workout, not even threshold. I don’t think I’d be able to complete 5.0 PL threshold workout.
It really helps me dial in workout intensities knowing how I perform in different kinds of workouts - helping me avoid burnout on sweet spot or threshold workouts, and dialing things up on VO2max or anaerobic.
1 Like
The ramp test, unless they have changed something, just gives you the FTP value as a set %, it is the same for everyone regardless of their ability to perform above ftp. I don’t believe there is any AI analysis of this going on at all.
Since we know that there is a large variance in people’s ability to perform above ftp, and because this varies throughout the season depending on what type of work the athlete is doing, performing an FTP test that actually tests ftp (not a ramp test) is always going to give someone a better number.
Sure you can wait for PLs to slowly adjust towards an accurate ftp but that is a waste of time when you could be performing appropriate workouts from the start.
The fact that PLs start adjusting things immediately after an ftp test is, to me, an indication that maybe the test is not terrible accurate for everyone.
You can see how large of a variance there is in people’s ability to perform above FTP here:
