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

Credit not given for new PR

First world problem here. I ran slightly longer than 5k. In the first 3.1 miles I clearly beat my old PR time. That 5k was part of a considerably longer run, so I know Garmin can pick out the record time even when the run isn't exact. (same for my 1 mile, 1k, 10k, etc.)

I'm not sure why Garmin Connect is not recognizing this new PR. I see that I can manually assign this as my new PR, but that only accounts for the entire time of the run, and with the extra distance, it's not accurate.

The pace for the entire run was 2 seconds less than the pace for my previous PR 5k. I only ran an additional .05 miles, so I know I think I can safely assume the pace for the first 3.1 is the same as the entire 3.15.

Anybody else see this?

0 WillNorthYork over 6 years ago

It's because you only ran slightly longer than 5k. When you run slightly longer than a given PR distance, Garmin Connect assumes you ran a race and uses the time for the entire activity as if you had run the PR distance, when considering PRs. This handles the case where you actually run races and your recorded distance is never exactly the same as the race distance. (Usually it's a bit longer.)

So unless your time for entire 3.15 miles was faster than the your current 5k PB, you wouldn't get a new record.

If you had run significantly longer than 5k, then yes, it would've picked out the PR for the exact 5k distance.

Some people don't like this scheme, but I think it's superior to Strava, where they always use the time for only the partial activity that matches your PR distance, so I have a bunch of "estimated PRs" which are slightly faster than my real-life race PRs.

0 markrobertburns over 6 years ago

sorry for slow "thank you" but thank you Will. That makes perfect sense, and I appreciate your response. I agree that it seems more rational than Strava since race distances are rarely perfect. I do like that Strava factors in TOTAL time when estimating PRs, however. It's all just for fun anyway, so nothing to get upset about.

Since then, I just went ahead and blew that time away, so it's no longer an issue (even when it was it was very very very very very minor. I had time, so I thought i'd ask)