|
Dec 2016
8:21am, 5 Dec 2016
7 posts
|
running_dan_w
HR training has been fantastically successful for me this year with PBs at every distance I've raced from mile (track & road) to half marathon.
The key is to understand your resting HR and max HR and then set your zones correctly.
The "standard" age calculation is often inappropriate. You'd also be surprised that your max HR is likely to be higher than you capture on even a hard run.
|
|
Dec 2016
9:16am, 5 Dec 2016
12,618 posts
|
mulbs
thanks guys - will investigate
|
|
Dec 2016
11:09am, 5 Dec 2016
5,874 posts
|
paul the builder
Going back briefly to mbln's question on the HR at the start of a run: one of the unintended consequences of Fetch's improvements of the presentation of the individual training entry pages - is that the graphs now have a fair degree of 'smoothing' built in to them. Which is fine when it comes to taking out the small noise of a pace or HR line that is just moving up and down slightly, due to natural variation during the run. But it can *hide* (disguise it by smoothing out) the bad data (big noise) too, making it look potentially OK.
You can change the sampling distance used for the graphs (it defaults to what it thinks is the most appropriate distance) - if you reduce it down all the way (is 10 metres the smallest?) then the lines get noisier and you can start to see if it's really spiky suddenly - a likely bad connection. Or a steadier increase/decrease - more likely to be what your HR was actually doing.
|
|
Dec 2016
11:28am, 5 Dec 2016
844 posts
|
mbln
Thanks for that Paul, hadn't even occurred to me that the data could be smoothed. It seems that this wasn't the case here - reducing the sampling to 10 mtrs shows a steady increase, then drop off after first mile - so not the 'normal' dry contact error. Unless this is the hrm-run version of that problem.
HR data back to expected this morning, and it's extra frosty so I think that rules out the cold theory.
|
|
Dec 2016
10:46am, 6 Dec 2016
37 posts
|
bakedbeano
Hi mbln, I used get this a lot with my tomtom cardio runner II, This watch measures HR at the wrist The first 5 or 10 minutes were obviously way high before it settled. I am a hairy soul and shaving at the contact with my wrist seems to have solved the problem.
|
|
Dec 2016
2:32pm, 6 Dec 2016
462 posts
|
Ulric
That's a new one for me beano 
|
|
Dec 2016
7:04pm, 7 Dec 2016
38 posts
|
bakedbeano
Hi Ulric, TomTom uses skin colour changes to measure HR , perhaps the hairs interfere somehow. Just read your summary. Top man well impressed with your recovery . So many people would stop doing the things they love on medical advice which is often given to cover the medics. they are always going to go for the safest option which doesn't apply to everyone.
|
|
Dec 2016
10:56am, 8 Dec 2016
468 posts
|
Ulric
yeah my consultant is a bit of a doom and gloom merchant who likes to tell me my heart doesn't beat strongly any more (technically I have left ventricular systolic dysfunction). I do have very poor peripheral circulation though and in hospital they used to struggle to get readings with a finger pulse oximeter which uses the same kind of sensor the TomTom does. I think.
|
|
Dec 2016
11:49am, 8 Dec 2016
39 posts
|
bakedbeano
Yet you are still running faster than I am with none of those things. Did have a large bleed on my brain 18 months ago and absolutely believe that getting back into running quickly helped my own recovery.
|
|
Dec 2016
11:53am, 8 Dec 2016
40 posts
|
bakedbeano
P.S I work in anaesthetics, Pulse oximeters work by comparing Infrared absorption at two different frequencies. Deoxi and oxihaemoglobin having widely different absorbtion spectra. (the beer-lambert effect)> Phew haven't had to explain that since I did my exams.
|
