Hello,
Is it possible to run the AI FTP detection over all my historical power data?
I like the AI FTP very much, because I hate all the all out tests.
The higher my FTP is the harder those all tests are.
I have 3 years power data, most outside. And started with TR in summer 2022.
Many thx
Christian
Iām no expert on the topic, but having listened to the TR team describe the AI FTP feature (just re-visited the podcast episode last night), they emphasized the following.
As for how to run an AI FTP calculation, believe it should be as simple as scheduling a ramp test, assuming you havenāt already done one within the last 14 days.
They introduce AI FTP right at the beginning of this episode. Good context and baseline overview of how it works.
Hi, Christian!
Iām glad to see you decided to upload all that history into TrainerRoad.
Your most recent training has the biggest impact on assessing your current fitness and FTP, so consistent ride data within the last year would be the most relevant for getting an accurate AI FTP Detection result right now.
However, that long-range historical data does help improve TrainerRoad models across the board, for everything from workout recommendations to FTP predictions. Thanks for syncing all those rides!
Stoked youāre with us, let me know if you have any questions about AI FTP Detection or otherwise. 
TR has almost 10 yrs of data on me. This includes rides <2018 when i had a different power meter ( left side only stages which is +20W than my current favero assioma dual-sided pedals).
Does aiFTP give much weight (more than 10%) to those old rides with inflated power?
So the ask is to get historical ftp levels so all the metrics that use ftp as part of the calculation can be more accurate? So less to influence what you are doing now but more to see your long term trends?
I like that idea. Even just the historical tss tr shows is kind of useless if your ftp is different significantly from the number it used to calculate tss. Then if you use more advanced metrics like what intervals.icu have can make it much easier to interpret the past
Yeah, thatās what I mean!
No problem! I think Im understanding that youād like to know retroactively what your FTP was at previous points in time. While this is not a feature that we have in place currently, Iāll keep an eye on this thread as a feature request.
Cool, Ivy!
I wonder what will be possible in the next year with AI!
Keep up the good work!
Christian
Not to worry, your immediate/recent training has the most significant impact on your AI FTP Detection result. Youāre all good!
I was wondering if those old rides with inflated power were the reason aiFTP decided my FTP was going āup up & upā 250 -->265 ā even 269 in Aug
vs how i felt (and ultimately tested) ānot so fastā 235W.
Anyway, iām sticking to 235W and not upping ftp until i can do Gray PL 5.9 (2x20min @235)
Very interesting this current communication!
@IvyAudrain Does AI consider if using in the workouts 10 sec back paddling or lowering the intensity some percentage?
Or does it only consider the responses like very hard or all out?
(I work myself in the AI field of SAP support and see always asking customers: what is it doing? Well, in many cases not really to explain because is self learningā¦
The duration and number of those backpedals can contribute to an interpretation of āstrugglingā, but that can also happen when you need to tighten your shoes, reach for a bottle, pause to stretch, etc. This is why youāre given the option to clarify that you didnāt struggle if those backpedals werenāt related to the difficulty of the workout.
Adaptive Training asking if you struggled based upon backpedals/intensity decreases varies so much depending upon the frequency and severity of both, and thereās no one all-encompassing formula such as āx seconds of backpedal = struggleā, or āx intensity decrease = struggleā. It gets very complicated in the context of each individual workout and what exactly youāre doing, but the good news is: AT is wicked smart when considering that. 
I feel seen. 
I would really like to be able to see what TR thinks my FTP would have been over time, even when I wasnāt using TR. One of the things Iāve always felt is a gap in my training is inconsistency in testing, so that it can be hard to tell what did and didnāt work.
Totally agree. Iāve previously asked for this for the same reason: to get a better idea of what has worked and what hasnāt.
I moved your post under a similar one from a while ago.
Iāll add my vote for retroactive aiFTP as a feature. Would be neat to see what aiFTP thinks it was relative to where I tested at.
I think people forget or donāt understand with ai or machine learning that itās all probability and model based. Thereās going to be times where that prediction is off, but it seems like with adaptive training that even with a mis-estimated FTP that oneās training plan will get brought back in to line within a couple workouts. Even as a scientist that deals with probabilities and statistical uncertainty all day, when it comes to training I have a hard time trusting the system. If I could just stop medaling with aiFTP detection as soon as Iām eligible every time, Iād be laughing!
For me the same. I think before TR my 20min or especially 8min test were really overestimated.I have a good anaerobic capacity FRC and when I was really fresh and motivated outside, I could smash this. 8min FTP was maybe 15 or even 20 watts over my feeled FTP.
This feature would be great to double check.
By they way WKO5 also gave me 10 watts more, if testing really hard.
Yep, thatās it, said more succinctly than I did. Iād like to go back and see what training correlated to changes in FTP and where FTP was for races.
@IvyAudrain As far as features go, I would think TR already has the work done, itās just surfacing all those grey diamonds, and is something that would get users spending a lot more time on the site and in the app.
