Related

Why run with pace 5.17 it is record, but run with pace 5.16 it is not. Look at print screen )

Fofcheh
4 months ago

Maybe 10.02 km  it is not enough distance to set a new record for 10km ?  Because , how you could see at print screens it was better time and better pace, but it was not record...

Top Replies

  • 3 months ago in reply to e7andy +2
    e7andy said:
    It seems like the records have a hard time when the distance is just at the distance for the record

    To expand on this, Garmin PRs work differently when you run close to the PR distance vs.…

All Replies

  • 0 4 months ago

    It seems like the records have a hard time when the distance is just at the distance for the record. Set it manually. Click the cog wheel > Set as PR.

  • 0 3 months ago in reply to e7andy
    e7andy said:
    It seems like the records have a hard time when the distance is just at the distance for the record

    To expand on this, Garmin PRs work differently when you run close to the PR distance vs. a bit further (or a lot further) than the PR distance.

    1) Close to the PR distance: the time for the whole activity is used

    (i.e. 52:53 for the 2nd activity)

    2) A bit/lot further than the PR distance: the time for the exact PR distance is used

    (In the 1st activity, if you ran 5:17/k for the first 10k, the PR time would be roughly 52:50, which would explain why 52:53 was not considered a PR.)

    A lot of people don't like this apparent inconsistency, but the point of 1) is to handle PRs for races, where ppl never run the exact race distance (they usually run a bit further.) 2) is to handle the normal case where you set a shorter PR during a longer activity.

    (Contrast with Strava, which always uses the exact distance for "best efforts". Every best effort that's set during a race will always be a bit too fast.)

    Even though Garmin tries to do the "right thing" with PRs, unfortunately it's unintuitive