-
Hi!
I’ve found out that Spartan Trainer calculates average running HR from the auto laps average HRs.
In my case, auto laps are based on distance (1 km), the last one is always less than 1 km of course.
Even if we ignore that last few hundred meters (last auto lap) have the same weight in the calculation as other 1 km laps, there is a flaw in this algorithm.
Not every 1 km lap is lasting the same time. When running uphill it can take much longer for 1 km than downhill. So taking every 1 km auto lap as a same for whole training average calculation is way off!
That’s also the reason there is a big difference between watch average HR and Strava or SportsTracker average HR for the same training.Is this a known issue, without a possible solution, because of watch hardware limitation? Or could it be solved in the future?
Thanks!
Darko -
Hi sorry but the avg hr is not coming from laps. It’s a continius calculation.
-
I’m sure my watch is using laps HR for the overall average HR.
I’ve attached images of watch laps and average HR of the training.
If I calculate the average from laps I get the same number. It’s the same case for other trainings. In Sportstracker the average for this training is 2 heartbeats lower.
-
@Dimitrios-Kanellopoulos Another example a day before:
Autolaps: 90+147+160+156+154+155+155+156 = 1173 / 8 = 146
Exactly the same number as average HR on the watch!
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login