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 misreporting swolf score

Former Member
Former Member
Hi,

I used my garmin swim for the first time today (loved it) but am a bit confused about some anomalies in the way it reports swolf scores

It is sometimes giving me a higher swolf score than the math (time plus strokes) would suggest.

and when I recorded each length as an interval it did the same thing.

see interval 11 on this swim http://connect.garmin.com/splits/298995247

I should have a swolf of 60 (43 secs plus 17 strokes) but instead it records it as 72

The same anomaly crops up in interval 3.

I should have a swolf for the interval of 68 but instead it gives me a swolf of 82.

Do the rest periods affect the score? Does anyone know what is happening?

Grateful for advice
  • Yes, that is weird. Thanks for reporting it. The rest periods should not affect the score. It would be helpful to have the original .fit file from the swim. I'll Private Message you about this (that makes it possible for you to attach the .fit file).

    By the way, it's great to see someone taking advantage of the 33 and 1/3 meter pool size setting (it was added in the last software update). :-)
  • Former Member
    0 Former Member over 12 years ago
    Swim number 2. Same problem (along with some lengths being counted as 2 lengths)

    Same problem with Swolf scores not being correctly calculated in Garmin connect.

    See interval 4 - I did a one length interval in freestyle - 40 seconds 17 strokes - correctly reported in both interval and length.

    But interval says my average SWOLF is 63, while length correctly identifies it as 57.

    fit file attached
  • Hi,

    I'm using Garmin swim for 6 weeks now and I notice the same problem everytime. SWOLF score is shown correctly in the lane row, but often incorrectly in the interval row!

    Can Garmin correct this or is there an explanation I don't know of.

    David
  • I don't really have anything useful to post on this but I didn't want to leave you hanging. We have figured out what is going on (so no more .fit files required - thanks) and it requires a tweak on Garmin Connect to correct it. As a user, there is nothing you are doing wrong and nothing you can do to correct it. I'm hoping to be able to report that it has been fixed soon.