Add reason why workouts changed when an activity causes adaptation

[enki42]

This is only for a subset of reasons as I’m guessing it would be very very hard to really add all reasons. But if an activity caused a workout to get easier because some extra activity caused TR to think you need something easier it would be useful to flag a workout has been made easier to account for fatigue.

This is somewhat based on:

AI FTP initially optimistic?

Love the AI FTP detection but wonder if it’s initially optimistic 28 days out and then converges to a more realistic number? I had a 239 estimate which landed on 222 (though this was when I first joined, so based on limited data). I now have a 241 forecast (currently 222 FTP) which would be another chunky improvement. I love the innovation though and it’s great to have something which reacts to each workout. One suggested improvement - a fuelling strategy for each session e.g. x grams of carb t…

In that it looks like when you fill in days between workout with other rides your workouts get easier to account for fatigue even if its not a switch to an endurance workout. It would be useful to know if the fun rides are causing an impact and if possible how much (if we aren’t racers but bike for fun we might want the tradeoff of having rides we enjoy even if it makes us slower)

[CliveW]

I always score outdoor rides as “easy” if they are on top of my TR schedule. This seems to minimise the downward ai adaption to the TR intensity.