The simulation window should be rolling. As it stands, the more time goes by, the less utility the window has. It doesn’t seem right that today, when I’ve just gotten a new FTP, I have a lovely 30 days to plan and adjust for fatigue, but in the last week I’ve just about lost the functionality.
2 Likes
yeah, that would more or less work. I can’t believe that this wasn’t a topic for discussion as they were designing this. The decreasing usefulness with each day that goes by is just odd.
To put it another way, it’s like you’re building up to a point (next prediction) that has nothing to do with your season goals, but is THE focus of your decision making in the app for the next 30 days.
Sounds like their might be technical or cost constraints, but a 60 or even 90 day window would be nice as well, even if it meant the predication was less solid the further out you go.
1 Like
Feedback received 
!
1 Like
The simulation rolls, but the prediction does not. Most of us are concerned with what our FTP will be at a date that is farther out.
A few of many challenges we’d run into with this are:
-
potentially greater sensibly to current workouts and the prediction could bounce around even more
-
Greater uncertainty in that longer term number
-
Increased computing costs to TR.
Knowing this, I’d still prefer the longer term estimate and would happily pay the additional costs.
1 Like
I dont know if there would be a cost difference, their model is refreshing every time I log into the platform, this would be similar, just with a different target date.
I agree, i’d like to see the constant “FTP in 30 days” type of box. As I got closer to my detection(tomorrow) it went from growing 18 watts to losing 1 watt. Love training for a month to get… less fit?
1 Like
It’s a compounding calculation that is done each time because it has to calculate what each workout will be to run the simulation. Right now the system has to calculate 14 days on average. If a prediction rolls at a steady 2 months out, that calculation moves from 14 days each time to 60.
1 Like
My FTP prediction is off but historically I know the range of increase for the end of the 28 day cycle. I also would find a prediction more useful to be at a set point in time. In my case this would be for before my cycling trip. Thats my focus but it is in June.
Adjusting work to optimize a 28 day point in time vs optimizing a planned event say 4/5 months may get us different plans. I also am upping volume as I go. I dont expect the software to do this as it is really more on how I feel then any guess on my fatigue.
I noticed that too; not sure why it’s needed if no activities have been completed since?
Might be a quick easy win to turn that off and only update on new activity, to save on cloud costs.
I misspoke about the fatigue window. I think a 30 day rolling for prediction would be good, and then 60 and 90 great too with accompanying caveats that they’ve got the potential to shift around.
1 Like