Metrics on new AI FTP Detection + TrainerRoad AI

@Nate_Pearson I agglomerated some concerns just in case. I think that for some people the new system goes into “TR burns me out” territory.

While my FTP estimate seams reasonable and pretty equal to the old AI FTP (I keep RPEing on the higher side)…meanwhile I’ve read enough posts as like the above that raise my eyebrows … and I share the concern of these users … but there needs to be a reason … is it high glycolic / anaerobic capacity people that can suffer through long above MLSS intervals … is it too low RPE ratings … or a combination of both … different power meters or different power outside vs inside … in either case I would not be happy if I got prescribed these workouts on that inflated FTPs…

I’m not sure if the system can self down regulate fast enough if you fail these workouts (?) because even if the AI prescribes by watt it is still tied to the plan structure…(now imagine being in Build with only threshold and VO2max) … so on threshold day AI is bound to threshold … so if it came to “realize” that it needed to drop intensity still is bound to a minimum of 95% of a potentially inflated FTP.

I’d definitely manually reduce FTP if I were one of the users above.

For me all this leads to 2 points:

  1. My tendency would be to align AI FTP around level 5 (but that has been mentioned enough already … so never mind)
  2. Decoupling AI workout prescription 1. from the rigid structure of the plans (and 2. maybe also from the workout library by generating individual workouts on the fly) (as already hinted but probably some time far away in the future)