PTE bug ?
-
Hello,
I’ve noticed a bug in the PTE calculation on my Suunto 9 peak pro (maybe since the last update?).
Sometimes, when I don’t have my heart rate belt on, I turn it off (so the heart rate is not recorded in my activity).
The problem is that a 10 km jog well below my maximum pace is always scored with a very high PTE score, often PTE = 5.I’d like to point out that I haven’t modified my parameters (heart rate ranges, maximum frequency, etc.). I’ve logged around 200-300 runs since I got my watch. So with the GPS and the calculation of my speed (which corresponds to my jogging pace) over less than an hour, there’s no reason to have such a high score. I take it this is a bug?
Thanks in advance,
-
@ventresca said in PTE bug ?:
I turn it off (so the heart rate is not recorded in my activity).
Well there is a known bug that turning off HR, isn’t actually turning off the OHR recording. Since OHR readings are so-so at best, just about any PTE can be shown.
-
@twekkel said in PTE bug ?:
Well there is a known bug that turning off HR, isn’t actually turning off the OHR recording. Since OHR readings are so-so at best, just about any PTE can be shown.
What is OHR ?
So, to sum up, you have a choice between :
- Run with the heart rate on your wrist (when you don’t have the belt) and get inconsistent data
- deactivate heart rate and get inconsistent PTE that break many other stats like health status, etc.
Shouldn’t this bug be fixed soon? Because it really breaks all the stats!
-
@ventresca OHR = Optical Heart Rate sensor
It should have been fixed asap IMHO, but it isn’t. I hate to see the complete bogus HR values in Strava and have to disable it for each and every activity.