This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Average Max power numbers

Former Member over 13 years ago

These are in some cases wrong. Simple as that. The numbers make no sense at all and are different from other analysis software I use (Golden Cheetah).

For example, for a ride yesterday I have a lap that is 13 minutes long and the average power for it was 292W. So the average max power for 13 minutes must be at least 292W. In Garmin Connect it claims the average max power for 13 minutes is only 263W. In Golden Cheetah (which has never given me any reason to doubt the numbers) the max for 13 minutes is 292W - entirely consistent with the lap average, unlike Garmin Connect.

So I don't know what Garmin are doing in calculating the average max power for different durations, but it's wrong. They have used the correct period to get the max, but the figure they report is wrong.

Anyone else find this?

0 Former Member over 13 years ago

A couple of examples:

20min max -- 259W, Garmin Connect claimed 20min max -- 236W

http://connect.garmin.com/activity/158091973

20min max -- 296W, Garmin Connect claimed 20min max -- 279W

http://connect.garmin.com/activity/159883679

0 Former Member over 11 years ago

Most probably you should change the option in your Garmin connect, under Power Average Calculations, instead of Use Zeros. In fact, Garmin includes zero-data power samples when calculating your average power. For example, if you go 50 seconds (providing 50 1-second power data samples), then pause for 10 seconds (providing 10 zero-data power samples), we divide the total power data by the total time (60 seconds) of your activity.

0 uffenl over 11 years ago

Most probably you should change the option in your Garmin connect, under Power Average Calculations, instead of Use Zeros.

1. This is not a changeable parameter
2. Golden Cheetah also uses Zero averaging

I'm pretty sure, that this is linked to the "time issue". GC has started again using "Elapsed time" rather than "Moving time" to fill the time field for .tcx imports. They claim the bug fix had other issues. The solution is to do a full edit and set "Time" to the value of "Moving time", then the averages should be re-calculated. It's been like that since 11 February with a small break when the bug fix was in force.