Garmin Connect web or android shows inconsistent vigorous minutes

First in "fitness age" shows "Increase Vigorous Minutes" a 6 week average but when you click through it shows the same value for a 4 week average.

The figure is neither the 4 week or 6 week average if you add up the the vigorous minutes (for 4 weeks or 6 weeks) that can be seen in the "Intensity minutes" section of the interface.

Also in "fitness age" shows "increase vigorous days" a 6 week average but when you click through it shows the same value for a 4 week average I have not checked these values but it's not possible to get 2.1 when dividing a whole number of days by 4. It seems likely this is really a 6 week average as 1/6 is .167 so 2.1 is possible.

0 7329009 17 days ago

I've also noticed this (actually I think many others have too).

I can mostly get matching values if I divide the 4 week total by 6. Except that, for example, intensive minutes during a walking activity are not included. Or at least it seems that way.

0 penyghent 7 days ago in reply to 7329009

They seem to of half fixed it.

The app now says 6 week average when I click through.

However, now that I can reasonably assume the figures are six week averages I can add up my vigorous minutes for each day for 6 weeks (back to 27 April right now - none on that day) and divide by 6. My calculate vigorous minutes are 75% more than shown in the app.

Vigorous days are much harder to calculate as the vigorous minutes may not make the 5 contiguous minutes. But on a quick guess as to whether a day did include 5 mins contiguous it would appear to be approx correct.

As for not counting walking activities. This is not the case as the vigorous minutes for my cycling activites surpass the figure shown (even when excluding the one when the watch died).

It seems to me that Garmin need to fix the calculation.

0 penyghent 5 days ago in reply to penyghent

Further investigation is that they are using the total of the last 28 days (obviously should be 42 days) and dividing it by 6 to get the "6 week average". A shocking piece of incompetence by whoever made the software change 4 to 6 weeks.