Not 935 specific but I'm posting this here because I think I'll get more attention with the higher percentage of users who do more "serious" training than other threads.
What do you folks think about having the ability to tell Connect to disregard the HR from a run or ride where HR results are seriously off due to cadence lock?
Today the temperature got up to a balmy 40f where I live so I went for a run in short sleeves and shorts, but unfortunately that was still cool enough to affect the optical HRM on my 735 and I ended up with an average HR of 184 when it was probably closer to 140 which resulted in a drop in Vo2Max of 2 points and left me with an extreme suffer fest Suffer Score when it uploaded to Strava.
I know that a single result can cycle out pretty quickly when only looking at Vo2Max but I wonder how it'll affect the Traing Satus/Performance stats that look more at the long term effect of individual runs. I don't normally look at HR that much during a run so I don't notice that I've got a run away HR until afterward so it would be nice it I could tell GC to ignore the HR for a run like that even if it is post fact.
Is it worth putting in feature request or will even the new stats see an easy run pace with a high HR get lost in the noise?