Seeing this error ("Error: Bad state: No element") when trying to edit one apparent mispunch from today's run - I've seen a few references to it in the forum search but not found an answer as to what's happened or how you get round it! MaprunG 5.0 (8), and the run was otherwise fine, no weirdnesses, everything seemed to go through as normal. Any ideas?
Hi. We'd need some more specifics to be able to check this out. Please let us know the event and the runner's name and confirm that MapRunG was used, and you are trying to use HITMO in MapRunF on your phone to edit the result from MapRunG (or alternatively describe the scenario if this is not it).
You can send these details to email@example.com.(or post them here).
Runner - Carrick Armer
Event is listed as 'SmelthousesNewYear PXASV PZ ScoreV120'
And yes, recorded in MaprunG, pulled down from there to MapRunF and trying to HITMO in MapRunF on my phone. Track is visible and result is visible but I get that error message when trying to bring up HITMO - it looks like the GPS had a wobble from the start (was running on road/track but the trace doesn't map to those.)
Hoping the GPS recording passes close enough to be able to claim Control 1 for that course - I know I was at the location but the GPS doesn't, apparently.
I've checked in the Admin version of HITMO (where Administrators can do similar things to what can be done by an individual with HITMO on their phone).
I initially received an error - and this is due to there being no punch on S1 (within the default 30m HITMO tolerance). If I increase the tolerance to 90m, at least in the Admin version, I can see the track... see image below. S1 at 31m and Control 1 at 65.9m.
So in terms of the error message - It looks like it is due to a missing S1 punch (at the default tolerance of 30m). I'll add this to my list of issues to improve in HITMO.
In terms of whether you should be credited with a punch on Control 1, I prefer to leave that to the event organiser to determine ... with their knowledge of the local terrain etc.
Thanks Peter, that's interesting. The watch had definitely pinged to signal a punch at S1 to start the course - though only on the second attempt admittedly, the first time I'd wandered up and down the road with nothing happening, stopped the app and restarted. The trace in Garmin Connect shows a 'kick' into towards the road which I assume is where that punch was interpreted to be.
The westward 'drift' seems odd though it could be environmental/terrain linked, but it had snapped back into place by control 2 and looked absolutely fine from there.
Off topic a bit but there were many reports of offset GPS tracks in the initial new year primarily from watches using the Sony chipset (most newer Garmin, some Suunto and other devices). Apparently there was an issue with the EPO file (Extended Prediction Orbit) that is downloaded on a regular basis by the watch (during syncs). It fixes itself once running for a while as the more detailed location data is downloaded from the satellites. Lots of factors playing into whether it impacted devices. DCRainmaker had a short post on it https://www.dcrainmaker.com/2021/01/gps-accuracy-impacting-devices.html