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

Associating a Personal Record with an Activity

NeilJonesOnline
over 10 years ago
I've only been using GC for a few weeks now, and despite the fact that I imported several thousand kms of runs from my old Nike+ account, I noticed that GC still showed blanks for my PRs. However, with a few GC runs under my belt, it's since populated the 5K and longest distance PRs using only the new GC data. I went out today to run a full-on 1K to use as a start-of-the-year benchmark, and ended up running 1.05K just to be on the safe side.

However, when I uploaded the run to GC, I didn't get the "New Personal Record" notification I was expecting, and it was still showing my fastest 1K time as blank. I went to put the time in manually, and noticed that there's an option to "Browse Activities", presumably to associate the PR with the activity rather than just enter the limited data manually. However, when I click on that, rather than being presented with a list of all my runs, all I get is a screen with just one run on from several years ago, on which I happened to run exactly 1K (in a slower time than today though). I can't find any way of getting today's run to show so I can use it for my PR.

Surely Garmin must realise that a distance PR isn't necessarily going to be set on a run covering only that distance? I think my fastest 5K was actually on a 10K run. Even if it does work this way, then surely it should still identify 1.05km as being a 1km run? Does this mean if I ever run a marathon, if I run 10m beyond the finish line before stopping the activity then GC won't let me associate it with a PR?

So, for my 1K run, is there any way I can associate it with today's activity, or am I just stuck with entering the time manually?

Thanks,

Neil
  • 0 over 10 years ago
    Surely Garmin must realise that a distance PR isn't necessarily going to be set on a run covering only that distance?


    Pretty sure they do realise that. I ran a 5k PB at parkrun last weekend and was also credited with a new mile PB and a new 1k PB for the same run. However, I seem to recall the 1k being a bit temperamental about populating for the first time when I started using my Garmin.

    Why not try manually assigning that 1.05k as your PB for 1k and then see if it updates thereafter on a subsequent faster run. Click on the "more" icon in the top right of the screen when that activity is open on screen, and select the option to assign a PR from the drop down menu.
  • 0 over 10 years ago
    I'm not sure why you would want records to populate from longer runs automatically - the main aim is that they should be runs of near to or exactly the target distance - otherwise that type of functionality is covered more in segments. What would be the point of me recording as a PR a 1M downhill stretch of a 10M run which I might run under 6 min mile pace whereas if I try and run a timed mile on the flat I am unlikely to run faster than 6:20?
  • 0 over 10 years ago
    Pretty sure they do realise that. I ran a 5k PB at parkrun last weekend and was also credited with a new mile PB and a new 1k PB for the same run. However, I seem to recall the 1k being a bit temperamental about populating for the first time when I started using my Garmin.

    Why not try manually assigning that 1.05k as your PB for 1k and then see if it updates thereafter on a subsequent faster run. Click on the "more" icon in the top right of the screen when that activity is open on screen, and select the option to assign a PR from the drop down menu.


    Thanks, looks like I'll have to do that - though "subsequent faster run?" - it could be some time!

    I'm not sure why you would want records to populate from longer runs automatically - the main aim is that they should be runs of near to or exactly the target distance - otherwise that type of functionality is covered more in segments. What would be the point of me recording as a PR a 1M downhill stretch of a 10M run which I might run under 6 min mile pace whereas if I try and run a timed mile on the flat I am unlikely to run faster than 6:20?


    I'd have to disagree - surely your fastest mile is, by definition, your fastest mile, whether it was a mile run or part of a longer run. I do accept your point that there might be certain situations where you'd want to "void" a new PR, such as a downhill, wind assisted or GPS errors, but when GC does identify a new PR it does give you the option of accepting it or not.
  • 0 over 10 years ago
    Why not try manually assigning that 1.05k as your PB for 1k and then see if it updates thereafter on a subsequent faster run. Click on the "more" icon in the top right of the screen when that activity is open on screen, and select the option to assign a PR from the drop down menu.


    OK, did that and it seems to have worked - the only oddity is that rather than extract my 1km time from that 1.05km run, it's actually giving my 1.05km time as my 1km PR so it's 10+ seconds wrong. It's more obvious on my half marathon record that I manually set the same way against an old 25km run, it's giving my time for that full 25km rather than just the "best" (or even the first) 21km (half marathon distance) of that run.
  • 0 over 10 years ago
    OK, did that and it seems to have worked - the only oddity is that rather than extract my 1km time from that 1.05km run, it's actually giving my 1.05km time as my 1km PR so it's 10+ seconds wrong.


    Sorry, I should have made that clear that it would do that. It was why I said see what happens when you run a faster one subsequently!
  • 0 over 5 years ago

    5 years later, this is still an issue...

    My GPS had an error so I recorded a too fast activity. I resolved the issues for said activity but never accepted or denied my PRs.

    Today, I ran an actual PR 10k and when I wen to accept my PR the old, faulty activity, was still there to be accepted or rejected. Of course I rejected it and assumed that the run from today would pop up. It did not.

    I tried to set todays run as my PR which apparently isn't possible from the app. Instead I went online and chose "set as PR" and chose 10k. Sadly, my run was a bit longer than 10k so my only option was to use the full run as a PR.

    There's three things to fix here:

    * When you update a faulty run so it gets new times/distances, it should not be prompted to set the old bad times as PR

    * When ju reject a PR, the next fastest run (if faster than the current PR) should be prompted

    * It should be possible to set PRs from the app

    * When setting a PR from a longer run, use the (fastest) cumulative time, not the time for the complete run.

  • 0 over 5 years ago in reply to bombsimon

    Why don't you edit, trim, or delete the faulty activity? It would fix all your troubles.

  • 0 over 5 years ago in reply to trux

    I did. I edited the activity (set the right distance, it was the GPS that bugged out) but kept the time since the time was correct. Now the distance and time for said activity is correct although I didn't find a way to change the splits.

    I still don't get prompted for todays PR. I still cannot set todays activity as PR from the app. I still cannot set the cumulative time of todays 10k as PR but instead get the complete activity which was a bit more than 10k as the PR time.

    Am I missing something here? How would I set the 10k cumulative time from todays activity as my 10k PR?

  • 0 over 5 years ago in reply to bombsimon

    Try exporting the faulty activity (to have a backup copy), and deleting it it from GC. Then make a minor change in the activity of the true record, to have it re-parsed. Hopefully it will be recognized as a record, which you can then accept. Consequently you can import back the deleted activity, and reject the record in it, if offered again.

  • 0 over 5 years ago in reply to trux

    Thanks for your tip, will try it out. Although even if it works it seems like a workaround more than a proper solution and I still think the bullets I made regarding what needs to be fixed is relevant.