Punching Controls
This page describes the rules MapRun uses in punching controls in the field. It essentially describes GPS-based punching, but the same logic is also applied to tag-based punching. (eg you can't punch the same control as you last punched).
The Definitive Guide to What MapRun Punches (and doesn't Punch)
In this guide when we say "MapRun", this applies to MapRun6 and MapRunG.
- MapRun will not punch if the GPS reports its accuracy at that instant to be worse than 50m
- For GPS-based punching, MapRun is continually monitoring the distance to controls. If the distance to a control becomes less than the "Punch Tolerance (m)" set for that event, the following logic is applied in deciding whether to punch that control or not. The default "Punch Tolerance" in MapRun6 is 15m radius, but this can be adjusted by the organiser of the event.
- MapRun will not punch any control before a visit to the Start. The exception to this is if the option in MapRun version 7 is set to "Automatically punch the start upon displaying the course". It is expected that this option would only be used in "Hunt Orienteering" where it is not required to visit the Start before punching controls.
- The Start is normally S1, but in an SAW (Start Anywhere) event, any control approached first (except F1), is renamed to S1 and is then punched as S1.
- The most-recently-punched control will not punch again until another control is punched (ie you can't punch the same control twice in sequence).
- S1 will not punch again.
- F1 will only punch after you have visited S1 and one other control.
- The correct sequence of controls on a line course is NOT enforced during a run. It is like normal orienteering, you can punch any controls in the field and the run is checked at the end. In an early version of MapRun we had a rule that the App would only punch the next sequential control on a line course. However, as soon as a runner misses one control ... nothing else will then beep. The App now punches all controls that are visited and handles loops in line courses correctly... with the validity of the result being determined after the event. (Like with SportIdent).
- Controls can be punched multiple times (but not in immediate sequence).
- In MapRun6, the count of punched controls is always incremented.
- In MapRunG, the count of punched controls is not incremented for a repeat punch on a Scatter/Score course.
- Nothing will punch after you have punched F1
Notes for course setters:
- Be careful with the location of F1. If a runner runs to the finish during a run, this will end their run. MapRunG now asks for confirmation of finishing (which the user must respond to before any other control can be punched) - but MapRun and MapRun6 finish immediately. See: http://maprun.308.s1.nabble.com/My-run-finished-when-I-went-to-the-Finish-F1-tp84.html
- Beware of setting courses with controls less than 30m apart. MapRun will punch two controls numerous times in rapid succession whilst the runner is in range of two controls. We could introduce logic to stop this, by disallowing punching of not only the most recent punch but also the one before it, however there are scenarios where this sequence of punching is valid. (And if there are three controls close together .....).
- If you want a loop in a line course, use the same control twice in the course file at the pivot point ... Don't put two different controls at the same location.
Background Discussion
MapRun can handle scatter, score and line courses including ones with loops/repeat controls. (Repeat controls are not allowed in scatter or score events).
Originally MapRun set up such that for line courses, it would only punch the next valid control on the course.
The problem with this was, if someone missed a control, then no other controls would register for the remainder of the course.
They may have accidentally missed the control and then be searching around near the next control site thinking they are just not at the correct location – not realising it is never going to register because of missing a previous control.
Also a control may have been setup in error or be inaccessible in the field. Then subsequent controls wouldn’t punch and so the opportunity to remove the one control from the results to get a “valid” result for the event would be lost.
Displaying messages/dialogs on the screen also doesn’t help as most runners don’t want to interact with their phone whilst running…. And so messages, warnings or requests for confirmation are ignored.
So MapRun now punches anything you go near, except:
- It will not punch controls before Start is punched and after Finish is punched
- It will not punch the Finish unless you have been to a least one control - This is how we allow for co-located Start and Finish.
- It will not punch the same control twice in sequence - This is how we avoid a steady stream of repeat punches when you are in the proximity of a control.
WARNING: MapRun will punch the Finish if you approach it mid-way through your course. Punching the Finish ends your run. Course planners need to take this into account in locating the Finish. See the new feature in MapRun version 7 for Confirmed Finish.
At the end of a Line Course (and other event types as well), MapRun analyses your series of punches and determines if you had a valid run (or not) (ie Classifiers: OK, MP, or DNF).
This is similar to SI and SIAir. Whilst in the field, you can punch any controls and whether you had a valid run is determined at the end.
MapRun changes the colour of controls punched on a scatter/score course from Pink to Green, but not on Line Courses (as it is not determining the validity of the punch on-the-fly).
Currently MapRun6 is changing the colour of the controls for all course types and so can give misleading indications. For example:
- punching an extra control on a line course between two valid controls will show it as green. If that control is actually on your course later, you might think you’ve already visited it
- when punching on ScoreB, in some cases it is impossible to determine if a control punch is valid or not until a subsequent control is punched (eg needing two evens in sequence), so again a control changing to green is not a reliable indicator of a valid punch.
The Definitive Guide to What MapRun Punches (and doesn't Punch)
In this guide when we say "MapRun", this applies to MapRun6 and MapRunG.
- MapRun will not punch if the GPS reports its accuracy at that instant to be worse than 50m
- For GPS-based punching, MapRun is continually monitoring the distance to controls. If the distance to a control becomes less than the "Punch Tolerance (m)" set for that event, the following logic is applied in deciding whether to punch that control or not. The default "Punch Tolerance" in MapRun6 is 15m radius, but this can be adjusted by the organiser of the event.
- MapRun will not punch any control before a visit to the Start. The exception to this is if the option in MapRun version 7 is set to "Automatically punch the start upon displaying the course". It is expected that this option would only be used in "Hunt Orienteering" where it is not required to visit the Start before punching controls.
- The Start is normally S1, but in an SAW (Start Anywhere) event, any control approached first (except F1), is renamed to S1 and is then punched as S1.
- The most-recently-punched control will not punch again until another control is punched (ie you can't punch the same control twice in sequence).
- S1 will not punch again.
- F1 will only punch after you have visited S1 and one other control.
- The correct sequence of controls on a line course is NOT enforced during a run. It is like normal orienteering, you can punch any controls in the field and the run is checked at the end. In an early version of MapRun we had a rule that the App would only punch the next sequential control on a line course. However, as soon as a runner misses one control ... nothing else will then beep. The App now punches all controls that are visited and handles loops in line courses correctly... with the validity of the result being determined after the event. (Like with SportIdent).
- Controls can be punched multiple times (but not in immediate sequence).
- In MapRun6, the count of punched controls is always incremented.
- In MapRunG, the count of punched controls is not incremented for a repeat punch on a Scatter/Score course.
- Nothing will punch after you have punched F1
Notes for course setters:
- Be careful with the location of F1. If a runner runs to the finish during a run, this will end their run. MapRunG now asks for confirmation of finishing (which the user must respond to before any other control can be punched) - but MapRun and MapRun6 finish immediately. See: http://maprun.308.s1.nabble.com/My-run-finished-when-I-went-to-the-Finish-F1-tp84.html
- Beware of setting courses with controls less than 30m apart. MapRun will punch two controls numerous times in rapid succession whilst the runner is in range of two controls. We could introduce logic to stop this, by disallowing punching of not only the most recent punch but also the one before it, however there are scenarios where this sequence of punching is valid. (And if there are three controls close together .....).
- If you want a loop in a line course, use the same control twice in the course file at the pivot point ... Don't put two different controls at the same location.
Background Discussion
MapRun can handle scatter, score and line courses including ones with loops/repeat controls. (Repeat controls are not allowed in scatter or score events).
Originally MapRun set up such that for line courses, it would only punch the next valid control on the course.
The problem with this was, if someone missed a control, then no other controls would register for the remainder of the course.
They may have accidentally missed the control and then be searching around near the next control site thinking they are just not at the correct location – not realising it is never going to register because of missing a previous control.
Also a control may have been setup in error or be inaccessible in the field. Then subsequent controls wouldn’t punch and so the opportunity to remove the one control from the results to get a “valid” result for the event would be lost.
Displaying messages/dialogs on the screen also doesn’t help as most runners don’t want to interact with their phone whilst running…. And so messages, warnings or requests for confirmation are ignored.
So MapRun now punches anything you go near, except:
- It will not punch controls before Start is punched and after Finish is punched
- It will not punch the Finish unless you have been to a least one control - This is how we allow for co-located Start and Finish.
- It will not punch the same control twice in sequence - This is how we avoid a steady stream of repeat punches when you are in the proximity of a control.
WARNING: MapRun will punch the Finish if you approach it mid-way through your course. Punching the Finish ends your run. Course planners need to take this into account in locating the Finish. See the new feature in MapRun version 7 for Confirmed Finish.
At the end of a Line Course (and other event types as well), MapRun analyses your series of punches and determines if you had a valid run (or not) (ie Classifiers: OK, MP, or DNF).
This is similar to SI and SIAir. Whilst in the field, you can punch any controls and whether you had a valid run is determined at the end.
MapRun changes the colour of controls punched on a scatter/score course from Pink to Green, but not on Line Courses (as it is not determining the validity of the punch on-the-fly).
Currently MapRun6 is changing the colour of the controls for all course types and so can give misleading indications. For example:
- punching an extra control on a line course between two valid controls will show it as green. If that control is actually on your course later, you might think you’ve already visited it
- when punching on ScoreB, in some cases it is impossible to determine if a control punch is valid or not until a subsequent control is punched (eg needing two evens in sequence), so again a control changing to green is not a reliable indicator of a valid punch.