MapRun score event - wrong timing for one competitor

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

MapRun score event - wrong timing for one competitor

d-dixon
Peter, all - have you seen this before?
One competitor's time was reported as 6 mins shorter than the elapsed time, and it looks like this was caused by incorrect timings for the last two legs.  The same competitor had a similar issue at their last event - where the time given between 2 controls was 0 s, instead of 5 mins.  
Before I manually correct this, could you please take a look?

Event: HH London Colney 2026
Runner: Ben Bardsley

Thanks! - David
Reply | Threaded
Open this post in threaded view
|

Re: MapRun score event - wrong timing for one competitor

Peter Effeney
Administrator
David,

Thanks for pointing this out.

I haven't seen this specific issue before, but I believe it will be a result of the MapRunG (Garmin) integration with MapRun.

As you may have seen in previous communications, we've needed to change the approach used with the FIT file from Garmin due to some changes in their back-end. This means that we don't now actually record the control Id's of the punches in the FIT file, and instead we need to retro-fit these in processing the FIT file in the "Get Track from Garmin" step. This seems to be working, but I have seen a couple of users where this has gone wrong in a couple of successive runs for them (therefore likely to be watch model / firmware specific).

If you could ask Ben to email me his FIT file, that would help with a deeper analysis.

Peter