Results showing zero time for some runners for last leg

[dfloat]

Hi,

We ran an event last night.  One of the runners (Sebastian Parris) is showing with zero time on the final leg (haven't checked to see if that is repeated for any other runners yet).  If I look at splits browser it has added a 15 min time for that leg.  But if I look at the strava log for that runner it should have been 1:18.






So, MapRun results showing time shorter than it should have been.
Splits browser showing time longer than it should have been.
Strava log showing correct time.

Any ideas what is going on?

Thanks,
David

[dfloat]

Update:
It is not only the last control, there are instances on the penultimate control as well.
Affecting runners on two courses last night, and on an event from two weeks ago.
But, some specific runners were fine on first event, but not last night

[Peter Effeney]

David,

Thanks for the report.

I expect that all of the cases involve MapRunG on a Garmin Watch. Please provide more details if not.

There have been changes in the format of the data in Garmin fit files that affects only certain watch type with certain versions of Garmin Firmware. This has resulted in anomalies like Zero times for all punches and in adapting to handle that, we have an issue with a small number of cases where the final leg shows zero time.

Our approach has been a combination of waiting for things to stablise at the Garmin end, and releasing new version of MapRun 7 that can handle the various cases that are identified.

When a case is identified, it is useful, if possible, to have the user get the fit file for the run from Garmin Connect on their PC/Mac and send it to [e-mail]  (in some places this is called the "Orginal

In the meantime, MapRunG users should check their results carefully, and if the result is quite wrong, use the GPS track to create a new result for the run using GPS Track Upload: https://console.maprun.net/#/gps_track_upload_without_rg
OR have the event Admin correct the result in MapRun Console.

We'll release another version of MapRun 7 soon that deals with another known case.

Peter

[dfloat]

Thanks Peter,

Most of these have occurred using MapRunG.  But I do know of one runner who only uses the phone and he has been affected.  He has confirmed he is still using MapRun 6

Details:
Name: Colin Jackson

Course: ChelmerV Oct24 Short
Control 11

Course: South Woodham Ferrers 2024 Short
Control 12

Kind regards,
David

[Peter Effeney]

David,

Thanks for the report - But I hope you will understand that we don't diagnose MapRun6 issues any more.

MapRun6 is no longer available in the App Stores.

MapRun 7 has been available since late 2022.

Upgrading is recommended.

Peter

[dfloat]

Yes, fully understand.

I have asked all affected runners what they are currently using.

John Carter, who has a 15 min leg on control 12 on South Woodham Ferrers 2024 Short, uses MapRun 7 on on iPhone 13.

Kind regards,
David

[Peter Effeney]

David,

The 15min leg is a RouteGadget "thing". If it can't work out a split it just defaults to 15mins for that leg (at least for the version of RG that I am using).

I suggest that if a result is a MP, then the RouteGadget splits are going to have weird things going on.

I shouldn't be too critical, as I have not developed a MapRun-native way of displaying splits. I should get on and do that. (The vast majority of MapRun events are scatter/score, and so splits are generally irrelevant.)

Back to the runner in question... If you are happy to use Admin HITMO and give him a punch on control 8, that will give him a valid run and I expect the splits will then make sense.



I've been progressively removing the connection to RouteGadget from MapRun. You've pointed out another good reason. I'll being the MapRun-native splits up the priority list.

Let me know if you have questions/issues.

Regards

Peter

[dfloat]

Thanks Peter,

So yes, if I Admin HITMO the "missing" controls then it seems to sort out the problem, and there is then no difference between the splits table and the MapRun results.

However, I can see the RG defaulting the 15 min even when a runner hasn't been to a control.  For example, Roy Read on South Woodham Ferrers 2024 Long, missed controls 6,7,8,9, and his track shows this.  So, he went straight from 5 to 10.  In the MapRun results it shows all the controls as visited, but with a mispunch.  In the RG table it is defaulting 15 min for those controls, so the overall time there is completely different.

I thought that in this situation in the past MapRun has shown a mispunch and just the controls that were visited, which then makes it easier to understand the results.  Presume the RG change has made this effect for MapRun as well?

Kind regards,
David

[dfloat]

I have just sent a Garmin Fit file for an example of a case where no time was recorded (we have since manually updated the time to match Strava).

Do you have an outlook for when the new version of MapRun 7 will be released?  Until then, if I understand correctly, the best approach is to review the splits table in RG to identify if any 15 min issues, and then to get a manual timing for anyone that effects?

The reason this is important is as shown in the following example:

Course: South Woodham Ferrers 2024 Long

MapRun results table shows Sebastian Parris as the winner.  However, this includes a zero time leg to the finish.  If I interrogate his Strava he actually took 1.25 for that leg, which if added to his time would place him second behind Chris Prince!



So, rather than just blindly take the MapRun results I think I have to interrogate each entry, see if there is a 15 min leg, and if there is go back and try to get a different timing for the runner?

Kind regards,
David

[Peter Effeney]

David,

That runner is using iOSMapRun10.0.6.
This was the MapRun version that was released on 30 Dec 2018.
Coming up 6 years old.

I think at the time, the focus was, let's get the display of results correct for a valid run and not worry too much about how MP's displayed.

There is a setting you can use to set the minimum allowed version of MapRun in an Event. I suggest it's time to set that to 7.0.0.

Peter

[Peter Effeney]

David

I expect another version of MapRun 7 in the next two weeks.

The only known issue affects runners using MapRunG (and only a small set of them).

In the meantime, you could download the results csv file for the event and you can see the MapRunG users and check their results.

Peter

[dfloat]

Many thanks Peter,

I will reinforce the instruction to use MapRun 7!!  

Thanks for your help.  Sounds like your new version will be released around the same time as our next event, so hopefully I won't have to do too much additional checking.

Kind regards,
David

[Peter Effeney]

David,

I have released MapRun 7 version 7.5.6 which has some improvements to the Garmin import (trying to cater for all known scenarios).

Even after someone has run with MapRunG they can try to Get Track from Garmin on their old version and if problems, then install the new version and try again.

Let me know if you still have issues.

Regards
Peter