Can’t you add “the why” to your notes on the workout?
I can, but as I understand the notes are really just for self-reflection & for others (TR staff etc) to place the effort in context of other stimuli on the day. I haven’t seen anything to suggest that TR’s ML system can read them & use that data to differentiate between activities that were hard because of intensity/duration (affecting FTP detection, RLGL, AT), & other stimuli that were perhaps unique to the activity. As an example, maybe that 45 minute .55 IF outdoor ride that should’ve been super easy, was instead moderate, because the athlete was kept up most of the night by a sick child. In this context the athlete is not going to be offered a struggle survey because Z2 rides only trigger them for “Hard”, “Very hard”, & “Maximum effort”.
Basically I’m asking for this as a means to help us remove noise from ML’s input.
1 Like
I guess I don’t see a distinction. Hard for your body is hard, no matter the cause. You either did the work and it took a moderate toll, or you did the work and it took a hard toll on your body. I am not sure that your body, and therefore FTP detection, RLGL, AT should care too much about the why.
I’d like the date format in the app to be user changeable to day/month/year instead of month/day/year.
3 Likes
The distinction I see is in whether it was harder than expected because of the workout itself, or because of circumstances that TR was unable to capture: diet, temperature/humidity/airflow, sleep (though capturing that in itself is a feature request), work/life stressors, equipment problem, etc.
If a coach gave me a recovery ride & I found it anything more than easy, they’d probably be asking me why. Similarly, marking a threshold workout hard has never triggered the struggle survey for me, even when its WL is substantially below my PL.
I’m just asking for a means to answer the struggle survey of my own volition, not every single time I do an activity.
3 Likes
Sometimes I’m in the middle of a workout trying to remember what workout level it is. Would love if that information was displayed next to or instead of the workout name. It is much more relevant info than the workout name to be sure.
3 Likes
I think Jetblack use it too… and I don’t even think you can turn it off…
I’d be supportive of this as long as it doesn’t increase the number of surveys at the end of normal workouts - i.e. if its an option that the athlete has to actively go in and edit after the fact.
2 Likes
I don’t think you are wasting your time - it’s great to have your opinions out there
However, I don’t think workout player UI improvements are high on TRs priority and you will probably find that the vast majority of current TR users are totally fine with that.
It’s basic, functional and uncluttered. It will also run on absolutely anything you can find with a Bluetooth connection.
It’s probably a bit jarring to new users but give it a few months and you will be converted…. or you will be doing your workouts using Zwifts (inferior 
) workout player.
4 Likes
The AI obviously thinks you have been sandbagging! 
2 Likes
I agree with all your points it’s more the way this is presented. The Wahoo desktop app UI is extremely similar and, while TR does many things better, the sensor value Vs target value in Wahoo is done more elegantly and, for new users, much more intuitively, without losing any information.
So agree 100% that a visual way to see the difference between sensor and target in real time is important. But think there are much better ways to present those data.
That would make sense as I read that the Zwift Hub is a rebadged Jetblack Volt V2
It would be very useful if we had the ability to move (or skip) scheduled de-load weeks.
The use case here is life will often force de-load weeks all on its own, but they won’t necessarily align with my TR plan. It would be great if I could just annotate a week as a planned de-load and the plan would properly adapt.
9 Likes
Thanks. I’m actually trying to keep my new user eyes as long as possible to spot these unintuitive things before I just shrug and get used to them. 
There is a scheme for auto detection - every 28 days - but maybe it is an idea to automatically just before (ond week or so) an A race update your ftp. For me ive had my A race last Sunday and can ask for a new ftp 4 days after my A race which I trained for.
probably one for the new feature request thread….. why would you want your FTP updated just before your A race?
As I see it, its been placed in the new feature request part. Regarding your question why, as an A race is the most important race and you want to race at a certain pct of your ftp to get the best results and race your personal max effort.
I meant the main feature request thread… but i’m not the police 
AI FTP on its own isnt really meant as a predictor of max efforts - but I could see why some people would like this.
2 Likes
I can see where this would be helpful when you are trying to pace at say .68 IF. It would be nice to have your most up to date AIFTP to set your Normalized Power target.
1 Like