I apreciate the HUD and that one could alter slots. But missing average heartrate. Average watt is of course valuble. Sometimes one´s daily form is more dependent of compared to heartrate.
/D
Hi @Dan3343_Gullmander welcome to Zwift forums.
Average heart rate for the ride is shown in the timeline graph for each session. You can see that in your Activity feed on both the website view and in the Zwift Companion app.
Don’t dox yourself.
Hi, thanks for your attention. Sometimes you must pinch yourself in the arm to understand that you are reading a seriously message correctly. That said. I´m no social media participant. Either and probably obviously not a fan of chat-threads, which often tends to carry away in all sorts of wrong and misinterpreted ways. Not the least the risk of hijacked threads for other topics. Why I posted my question in Zwifts forum was because I was advised to do so from Zwift when I emailed this subject directly to them. That´s the background…
Well, your answer suggests that my question is about seeking average heartbeat overall. I can´t see how that could be an issue? Most zwifters are well experienced seeking data in both the web- and app versions. So, to say afterwards of their training. Of course, I do too. It´s a habit for me to evaluate my training afterwards.
So, your answer is a bit odd. I read a consideration in the answer, but it tends to reduce my real intention to an issue of pure information.
Frankly, I hesitated to answer you. I mean. You may see the information you give me as informative but also reveals that I as a barer of question has serios lacks in my understanding with Zwifts data. I don´t. I consider myself to a good user of Zwifts’ diverse ways of showing data.
So here is my original question again in more fully context. The HUD is a data-form presented while your exercise. It has four slots, each selectable what to show. But in this shape, it thus lacks average heartrate. One could of course argue this request is farfetched. That average watt that is for instance presented in the HUD is good enough. Of course, it´s appreciated. But most trainers are not that accurate in their watt-values. Mine for instance. Thereto watt is an empirical data not always corresponding with your physical form. Not to mention your daily. I trained for 20 years and therefore know what my average heartrate corresponds to my daily form. One day – say – 80 % av maximum (heartrate) therefor corresponds with – in my case – 190 watts. Next day it corresponds with 175 watts. Since I now can´t read my average heart rate until afterwards I can only trust my feeling that a worse physical day experience is too hard even if my watt-numbers are more modest. The risk is staring only at these watt-numbers, I submit myself to too hard training when I instead should ease off.
In most training circuits watt is the new religion. But seldom does one hear that it´s a data calculated value which assumes of certain relationships between effort and in this case watt. Watt is of course dependable. But again, daily form, miss calibrated or moreover unreliable trainer watt-measuring have given me a critical attitude to blindly trust watts. Therefore, when the HUD was introduced as an update in Zwift, it really was appreciated to at least read average watt which earlier only could be read afterwards. Since the HUD has four slots, each – as I wrote, with selectable data but currently not average heartrate that I really, really should appreciate in a future update. To read average heartrate during exercise is a key for hopefully more participants to calibrate them self and their effort on the fly.
High heartrate is more accurate than high watt. If the average heartrate moreover tends to stay at high values into an exercise (from the start and does not reduce), it points out something crucial. As I said, either to ease off or to back away from a certain event, if one, as I frequently do, participates in races.
Thanks, Dan
Average heartrate is useful?
If I want to do a ride at 130bpm i’ll just warm up and then try to stay between 125 and 135 based on the in the moment HR shown on the HUD.
Let’s face it - I could do 160bpm for 3 minutes alternating with 100bpm for 5 minutes and average 130bpm, but it would be a wildly different stimulus to a nice steady ride btwn 125bpm and 135bpm!
I have my Wahoo Bolt set up to show that. No idea if a bike computer is an option for you, but if it is, that might help.
I’m with you on this and I’m a runner.
Average HR as a metric is ok for post activity analysis but during activity live data surely is better. Like you say average doesn’t take into account warm ups and as you’ve demonstrated you could be well over or under your intended target but still maintain that average.
Most prefer to stay in a particular zone which using the colour HR blocks is simple.
Or do an activity where they don’t exceed a HR figure.
I can’t recall seeing any workout or plan that says to do an activity to an average HR.
1 Like
Well, it´s a way of handling things. For sure useful if that´s a question. It certainly wasn’t mine. Mine was about suggesting something for Zwift to implement. But then again. Each interpret what occurs to them.