Having been ill for a week the RHR is all over the place - 30% up on normal. Is there a way I can level this/fix it so that the calculations start again from before when I was ill? I don't want to wipe out the other activity data though.
What's there to fix, if it's a true record? The point of gathering data is not so the graph looks pretty or the conclusions drawn from it flatter the user. ‑
HOWEVER... if the values are INCORRECT, that's a different issue. Like for me some days it lists a RHR of 37.... and I can't find a value that low during the entire day on the graph! Other days I can find long periods of 42-46...yet my RHR for the day is 56... it's almost like it is chosen from random some days!!!! Which then totally alters the weekly or monthly average when looking back.
Typically it appears it is ONLY chosen from sleeping periods... however my HR floats all over while sleeping. Often my sitting in traffic or chilling on the couch my HR will easily be 5-13 beats lower than many days sleeping. Other unchangeable attributes like vo2max sure would be nice to be able to at the very least 'remove' the data point.... better yet edit them like you can with the Sleep data.
Lately it seems vo2 max readings are very up and down - one run with significant wind while overdressed.... will drop it.... or runs in the snow / trails/heat for a week will skew it as well. Would be nice for long term tracking... to be able to clean up the anomalies.
My Wife has a 235, I myself have a 620 and VAHR. One of the reasons I bought the VAHR was because of the RHR. Unfortunately it's not as good as I hoped. It spikes quite often (sometimes 39, sometimes 61.). Not every day, but often enough. Also it seems to have problem with me working shifts. When I come home from work shortly bevore midnight and I lay down to bring my HR down (or try to), it sometimes "corrects" my RHR (for example from being 62 down to 56), If I don't do that or if I work until after midnight, no such correction occurs. But when I check my RHR just after waking up on either day, it usualy is around 53/54... What also seems to impact RHR is when I get up early (around 4 / 4:30 am). Usualy my RHR according to my VAHR is also higher then. But frankly, I have not found any real/consistent pattern which could explain these spikes. So, RHR for me is not as useful as I hoped (I use it especially to monitor my health, because I tend to get sick very quickly, unfortunately). The good thing though is, that with the VAHR it's easier to check my RHR after waking up and the long term averages at least come close to what my RHR really is. Still, I whish RHR would be more accurate (on the VAHR, at least. It's hard for me to tell, if my Wife's 235 is any different).
There appears to be two different algorithms Garmin is using to find RHR.
If you wear your watch during sleep time, it appears to average out your low readings, whatever that means. This gives me readings about 5-10 BPM higher than what I've observed and manually measured.
If you don't wear your watch during sleep time, it seems to take the lowest observed reading. This seems to track better with my manual in bed awake readings.
For me, I get more accurate results if I don't sleep with the watch, but then I don't get sleep information. One way I've gotten good numbers with sleep info is to sync my watch when I wake and then cycle the power. This seems to restart the RHR cycle.
I don't have any answers but would like to add my disappointment at the RHR algorithms.
I was looking forward to looking at trends but the values just seem made up.
Would be interesting to see what they would be like if garmin gave the option to do full 24/7 sampling as it was in the early firmwares. I always feel cheated that was taken away and don't understand why garmin will not give it back as an option.
I have even considered wearing another device on my other wrist for hr and sleep as garmin just don't seem to be able to get either right.
Incidentally I have a 735 with measures lactate threshold. When it detects a new value it asks if you want to accept it.not sure why it doesn't do that with vo2 max. As you say I have had the odd run where hr hasn't locked properly and it makes no sense to update vo2 max off it.
Incidentally I have a 735 with measures lactate threshold. When it detects a new value it asks if you want to accept it.
That's interesting. On my FR630, the device simply informs me if/when a new lactate threshold has been detected (which happens after almost every session for me).
That's interesting. On my FR630, the device simply informs me if/when a new lactate threshold has been detected (which happens after almost every session for me).
It definitely does. I only have 2 recorded in garmin connect. One when I first got the watch and another after I did a proper guided test on the flat.
I rejected all others. Mainly as I don't trust the results on any run that is not on flat terrain. As the 735 doesn't have an altimeter I just don't see how it can calculate it accurately if hills are involved. I intend to do regular tests on a flat route instead to see how it is trending.
The same applies for vo2. In fact I am surprised they calculate it on the watch and don't do it at the connect end once they have plotted the elevation from mapping data. It would also survive a hard reset that way also.
The same applies for vo2. In fact I am surprised they calculate it on the watch and don't do it at the connect end
Whereas I'm not. Licensing considerations trump preferences to include more data for supposedly improved accuracy any day.
It would also survive a hard reset that way also.
That's hardly a concern, when I basically get VO[sub]2[/sub]max (re-)evaluated with every run, and the watch has zero need for previous estimates for any new calculations. The user has access to past estimates which have been transferred to Garmin Connect for his/her account, and these do not get lost or overwritten by a hard reset of any Garmin device.
That's hardly a concern, when I basically get VO[sub]2[/sub]max (re-)evaluated with every run, and the watch has zero need for previous estimates for any new calculations. The user has access to past estimates which have been transferred to Garmin Connect for his/her account, and these do not get lost or overwritten by a hard reset of any Garmin device.
I've always thought, that VO[sub]2[/sub]max takes a while, like a couple of weeks, to get proper readings/settle down (ok, my only source for that is dcrainmaker and my knowledge regarding this is quite limited)? But if that would be the case, wouldn't a hard-reset have an impact on the VO[sub]2[/sub]max value?
Mainly as I don't trust the results on any run that is not on flat terrain. As the 735 doesn't have an altimeter I just don't see how it can calculate it accurately if hills are involved. I intend to do regular tests on a flat route instead to see how it is trending.
Then I'm scr*wed, no flat terrain where I live :D But good point, never considered that.
The same applies for vo2. In fact I am surprised they calculate it on the watch and don't do it at the connect end once they have plotted the elevation from mapping data. It would also survive a hard reset that way also.
I'm glad it is calculated on the watch, as it would make me more dependant on having to be online (to sync) to get the data. Though, if it would be calculated on Garmin Connect, couldn't it then be opened up for every HR-Capable watch? I wonder if that is even possible.
