Checking Results

Once an event has been concluded, it is recommended that the event organiser (or MapRun Administrator) review the results for any anomalies.

The first step in this is usually to review the Leaderboard including sorting the key columns to identify any outlying results. For example:

• Zero controls visited
  • This can sometimes be the case where someone had a "false start". There may be another result for them in the table of results and so this result can be deleted
  • Alternatively, it might be that there was a malfunction, and the process of dealing with a partially completed result may be appropriate. The Administrator could upload the track as a GPS track to create a new result if required.
• No track for a runner
  • ​If there is no link to a runner's track, it is recommended to firstly, refresh the results using the Admin Function
  • This will not resolve the matter if the root cause is that the runner's upload was only partially successful. A normal upload of results posts a CSV result file and a GPX track file to the server. If the GPX track file failed to upload successfully, the runner may need to reopen the results on their phone and manually upload the results with the "Upoad Results" button. Multiple uploads of results do not cause a problem.
• ​Not all controls were registered for a runner
  • ​A runner may alert event organisers to a case where they visited a control site but MapRun did not register that control.
  • In such cases:
    • ​Inspect their result on their phone. See if the track shows the runner going to a control that was not registered. For scatter and score events, the registered controls are shown in green.
    • Alternatively the track can be inspected in the RouteGadget display (accessed from the Track link in the Leaderboard table of results).
  • ​It is recommended that Administrators use the "Results Validation" tool which allows for a quick overview of all runners in an event. It shows all approaches close to controls and whether that control is in the results or not.
    • ​The Administrator can adjust the tolerance of the analysis
    • Controls shown in Red should the focus, however, not all controls shown in Red should be considered as a problem. For example:
      • ​Approaches to controls before visiting Start are shown
      • The visit may be a duplicate visit
      • The visit may be a run-past on the way to another control (eg in the case of a line course)
  • ​​The Results Validation tool can be accessed at: http://www.p.fne.com.au/rg/cgi-bin/ResultValidation.cgi
  • Note that this tool does not edit the results, that still requires the Administrator to use the Results Editing Function.

Please report any issues via email to: support@maprun.net