Related
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

Personal records calculation

Former Member
Former Member over 5 years ago

Hello everyone

 I wondering about the calculation of personal records,

I did a run of 10,08k in 41'29", so in average of 4,07min/km.

During this run, there no big speed variation except the final sprint at 3,30min/km during 20 second.

In my personal records, I see my records for 10k in 41'28".

If I take the average speed (4,07min/km), my record for 10k is 41'10"

How are personal records calculated? 

If you have any explanation...

Thanks

Julien

  • 0 over 5 years ago
    How are personal records calculated? 

    The time for the 10km must be in one chunk. So for example when the starting and the final parts of a run longer than 10km are fast, then the algorithm will take the fastest 10km chunk from the run, but the average can be easily faster, if the slow part was somewhere in the middle and hence cannot be excluded.

  • Former Member
    0 Former Member over 5 years ago in reply to trux

    Thanks for you response, 

    According to you explanation and my run review(on the picture), I think there is a little bug: the fastest 10k is in 41'14" ( or may be faster but I can't see this without big calculation)

    Do you agree?

  • 0 over 5 years ago in reply to Former Member

    And what does the Running tab in your Personal Records page show? Did not you reject, or omit to approve the new record?

  • 0 over 5 years ago in reply to trux

    You can also try going to the concerned activity, and in the context menu under the cogwheel symbol (up right), select the option "Set as PR" - and see what time it shows then on the PR page.

  • Former Member
    0 Former Member over 5 years ago in reply to trux

    Yes, I approved the RP yesterday ( so more than 12 hours ago)

    Thank for the trick! I did the manipulation but the RP stay the same...

  • Former Member
    0 Former Member over 5 years ago

    I think I found the response:

    L"records personnels sont créés lorsque vous téléchargez des données qui correspondent étroitement à l'une de nos distances prédéfinies, et qu'il s'agit de votre meilleur temps téléchargé pour cette distance.

    La distance ne doit pas nécessairement correspondre exactement, mais elle doit être proche. (Par exemple, un record personnel de semi-marathon peut être créé pour une activité de 13,2 miles). Connect recherche un record personnel uniquement lors du premier téléchargement d'une activité. Une activité modifiée ne sera donc pas répertoriée comme un record personnel."

    To explain, the distance of a run is approximate. In my case a 10,08k is approximate to a 10k and there is no time adjustment.

  • 0 over 5 years ago in reply to Former Member

    No, it is not really what the description tells. It just tells that the distance of the activity does not need to match exactly the given record distance (10k), and that manual changes won't have impact. However, normally, the algorithm still searches the best exactly matching section within the activity and proposes it as a PR. I just checked couple of my previous activities with records - for example I had new 1km, 1mile, 5km and 10km records in one activity, and each of the PR respects the fastest section within the run (it was 17km long in fact).

    In my case it seems to work correctly, so I do not quite understand why it did not work in your case. Unless you edited the activity manually, but I do not think you could edit the lap times, unless you imported the run from an external file, which I suppose is not the case.

  • Former Member
    0 Former Member over 5 years ago in reply to trux

    Indeed, you're right, 

    Moreover, the run has not been edited or imported,

    Thanks you for your time, I will contact the support to notify them ( In case of other person have the same problem).

  • 0 over 5 years ago in reply to trux

    .. thinking about it again, it can be perhaps depending on the watch model - records are (at least partially) managed by the device, so it is possible that it is your watch that calculates the fastest section differently than mine. The fastest sections are then perhaps stored in the fit file, and the GC account just displays them. That's the only explanation I can find, that would explain why the fastest 10km section was not detected in your activity, while it works all right for me. What device do you use? Is it an older model, or a recent one?

  • Former Member
    0 Former Member over 5 years ago in reply to trux

    It might be this!

    I use the Forerunner 235 with the last update,