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

Garmin Connect forgotten how to do Math?

Former Member over 13 years ago

Hi everyone!

I have a Garmin Forerunner 210 and since the latest Garmin Connect update I'm seeing some odd Math.

Activities from Tuesday, Wednesday and Thursday all have the new 'Training Effect' listed but the value is always '.3' (i.e. In words: zero point three). Previously, I've never seen this 'Training Effect' before. Since my device doesn't calculate this, I have to assume that Garmin Connect itself is. I find it hard to believe that Wednesday's 10km interval session (8 x 800m run/400m jog) where I beat myself up (and my heat rate peaked at over 180 bpm and averaged 167 bpm) had less than a 'minor' training effect. :confused:

Then when I uploaded today's activity (Friday), there is no 'Training Effect' and my average pace/speed is incorrect. I ran 6.27km in 28:09 - but Garmin Connect tells me that is 5:33 min/km average pace. Surely, something around the 4:29 min/km is correct.:rolleyes:

Any ideas Garmin?

Cheers,
Damo.

0 BBECKER39 over 13 years ago

This value is showing up in some Forerunner 210 activity files even though it does not calculate this metric. This is a device firmware bug. Garmin Connect is not attempting to calculate a Training Effect value from your workout.

0 Former Member over 13 years ago

Thanks for the clarification on the Training Effect, BBECKER39. Any idea what's going on with the average pace calculation in this activity?

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

0 ACESYMMETRIC140 over 13 years ago

Thanks for the clarification on the Training Effect, BBECKER39. Any idea what's going on with the average pace calculation in this activity?

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

I assume you are referring to the Overall agv of 8:56 vs the lap pace averages ranging from 7:10 to 7:20.

If you look that the chart there is a 14 second period of time where your pace started at a 30 minute mile. It is possible that this may have skewed the overall agerage. To prevent this make sure you have a good satellite fix before starting your run.

0 Former Member over 13 years ago

Yes, Stacey - I'm referring to the overall average pace.

I don't see how the 14 seconds at the start can make such a marked difference. Surely overall 'average pace' means overall average pace...

...and if that isn't something close to the total time (28:09; converting the seconds to decimals = 28.15) divided by the total distance (6.27km), then I need to go back to school.

For the record, that calculation yields 4.49 min/km; converting back to minutes and seconds = 4:29 min/km (not the 5:33 min/km Garmin Connect is reporting).

0 BBECKER39 over 13 years ago

The pace numbers you see are from the device, so the error occurred there. What caused it, I don't really know. If you look at your average pace for each split, they are all right at about 4:30. It then claims an overall average of 5:33 which is clearly wrong as you have noticed.