Confirmed Finish (MapRun v7)
MapRun v7 introduces a new option for Admins to set a “Confirmed Finish” for an event. This is designed to avoid “accidental” early punches of the Finish control (F1).
Subject to a successful period of evaluation, the plan is for this to become the default option for new events.
Summary Description
If you accidentally run past the Finish, you will get a special sound (4 chimes) and have the option to cancel the punch. If you have your phone in hand, tap Cancel, OR you can just keep running for at least the next minute and the punch will be automatically cancelled.
No change is proposed for MapRunG which already asks the user to confirm they are finished. This is consistent with how Garmin normally asks the user to confirm the finish of an activity.
The general advice continues to be, that organisers should layout their courses in a way that avoids accidental visits to the Finish during a run (as would be required for SI-Air punching (SIAC) as well). For the low number of occasions where a participant accidentally visits the finish early, “Confirmed Finish” operates as follows.
Details of Confirmed Finish
Upon approaching F1 (with GPS-based punching) or scanning the F1 QRcode or tapping the F1 NFC tag:
1. If Confirmed Finish is OFF, MapRun will operate as it does currently, that is, punch F1, finish the event and show the result.
2. If Confirmed Finish IS ENABLED for this event, the punch will be treated as an interim punch.
MapRun will:
- record the time (as the time of the interim punch),
- vibrate/beep in a new distinctive sound (Chime sound 4 times)
- display a message on the screen asking the user to Confirm or Cancel the punch of Finish.
- continue tracking and timing the participant.
3. The message will remain on the screen for 60 seconds. If:
Subject to a successful period of evaluation, the plan is for this to become the default option for new events.
Summary Description
If you accidentally run past the Finish, you will get a special sound (4 chimes) and have the option to cancel the punch. If you have your phone in hand, tap Cancel, OR you can just keep running for at least the next minute and the punch will be automatically cancelled.
No change is proposed for MapRunG which already asks the user to confirm they are finished. This is consistent with how Garmin normally asks the user to confirm the finish of an activity.
The general advice continues to be, that organisers should layout their courses in a way that avoids accidental visits to the Finish during a run (as would be required for SI-Air punching (SIAC) as well). For the low number of occasions where a participant accidentally visits the finish early, “Confirmed Finish” operates as follows.
Details of Confirmed Finish
Upon approaching F1 (with GPS-based punching) or scanning the F1 QRcode or tapping the F1 NFC tag:
1. If Confirmed Finish is OFF, MapRun will operate as it does currently, that is, punch F1, finish the event and show the result.
2. If Confirmed Finish IS ENABLED for this event, the punch will be treated as an interim punch.
MapRun will:
- record the time (as the time of the interim punch),
- vibrate/beep in a new distinctive sound (Chime sound 4 times)
- display a message on the screen asking the user to Confirm or Cancel the punch of Finish.
- continue tracking and timing the participant.
3. The message will remain on the screen for 60 seconds. If:
- Another control is approached - The interim punch of Finish would be dismissed and the latest control would be punched. This is the typical scenario of a runner accidentally passing Finish on the way to another control.
- The participant, taps the Confirm button to confirm the interim punch of Finish. MapRun would punch F1 (usual vibration and sound) and record a Finish at the time of the interim punch.
- The participant, cancels the interim punch of Finish. MapRun would remove the interim punch and continue the Event. Note that in this scenario, punching of Finish is inhibited (to avoid it punching again immediately), until another control is visited.
- At the end of the 60 second period, the message will be removed and if the user is still moving (at at least half their average pace between Start and Finish):
|
From a user perspective
What can go wrong?
What if you make the wrong choice?
Reviewing what happened
If you would like to review the sequence of steps/events that occurred in a Confirmed Finish, MapRun logs each step. The historical log is available from the home screen of MapRun. Select from the Menu “App Event Log”. This shows the sequence of steps that have occurred.
Background and Recommendations
The “Confirmed Finish” option in MapRun v7 aims to eliminate accidental early visits to the Finish, typically caused by a route choice between controls that goes near the Finish.
For events where the organiser has switched on “Confirmed Finish” in MapRun v7+, if the participant approaches the finish they will hear an unusual sound at the Finish: 4 Chimes in quick succession and a prompt will appear on their phone.
If this is an accidental visit to the Finish, it will be cancelled if:
- they keep moving at a similar pace as before, for the next 60 seconds, or
- they punch another control, or
- they tap “Cancel” in response to the prompt on the phone.
If, on the other hand, they are wanting to finish, the punch will be confirmed if:
- they tap “Finish” in response to the prompt on the phone (in the following 60 seconds), or
- they stop running/walking for the following 60 seconds (That is, their pace should be less than half of what they were doing between Start and Finish).
After 60 seconds, they will hear the normal beep for a punch of Finish. Their time will be recorded as the time they first approached the finish.
With “Confirmed Finish” the only ways in which an “accidental punch of Finish” can occur are:
- all controls have been visited (so it’s probably not “accidental”), or
- the time in a Score event is past 90% of the allowed time (or overdue), or
- the user taps the Confirm button after an unintended visit to the Finish, or
- the user does not respond to the prompt to Confirm/Cancel within 60 seconds and slows/stops in that period.
If a participant accidentally visits the Finish, do they need to take any action when they hear 4 Chimes?
- If they don’t want to Finish, they can keep walking/running at about the same pace as they were previously and the interim punch of Finish will be cancelled at the next control (or after 60 seconds). They need to visit at least one control before coming back to Finish.
- Otherwise, if convenient, they can tap the “Cancel” button on the phone.
- As always, we recommend that unless they are carrying your phone in their hand, that they blank the screen to avoid any accidental input to the phone.
Flowchart
For those people who would like to see the logic of Confirmed Finish in a flowchart:
- If you accidentally run past Finish during an Event, you will hear a distinctive Chime sound (chime sound 4 times). If your phone is handy, you could cancel this punch. Otherwise, just keep moving and MapRun will cancel this punch when you visit another control or after 60 seconds and you are still moving.
- If you run to the Finish control to finish your run, then the punch will be treated as an interim punch and you will be asked to confirm it on the screen of the phone. If you don’t confirm it within 60 seconds and you have stopped moving, the punch will be confirmed automatically. Otherwise the punch will be immediately recorded as a confirmed Finish.
What can go wrong?
What if you make the wrong choice?
- If you accidentally visited the finish and you are prompted to confirm/cancel the finish, and you accidentally confirmed it (when you didn’t mean to), sorry, but the event is over for you.
- If you are wanting to finish and you are prompted to confirm the finish and you accidentally cancel it,
- If you are wanting to finish and you are prompted to confirm the finish, you take no action and after 60 seconds, MapRun thinks you haven’t stopped, it will have cancelled the finish.
- In either of these two cases the timer will be still running. To fix this, exit from the run screen (using the Home icon on the top left). Then use HITMO to treat the approach to the finish control as a punch.
- Note that in these cases, it is NOT a matter of simply re-visiting the Finish, as punching the Finish will be disabled at this point (unless you visit another control after Finish). Also, you would like your earlier visit to Finish to be recorded as your finish time anyway.
Reviewing what happened
If you would like to review the sequence of steps/events that occurred in a Confirmed Finish, MapRun logs each step. The historical log is available from the home screen of MapRun. Select from the Menu “App Event Log”. This shows the sequence of steps that have occurred.
Background and Recommendations
The “Confirmed Finish” option in MapRun v7 aims to eliminate accidental early visits to the Finish, typically caused by a route choice between controls that goes near the Finish.
For events where the organiser has switched on “Confirmed Finish” in MapRun v7+, if the participant approaches the finish they will hear an unusual sound at the Finish: 4 Chimes in quick succession and a prompt will appear on their phone.
If this is an accidental visit to the Finish, it will be cancelled if:
- they keep moving at a similar pace as before, for the next 60 seconds, or
- they punch another control, or
- they tap “Cancel” in response to the prompt on the phone.
If, on the other hand, they are wanting to finish, the punch will be confirmed if:
- they tap “Finish” in response to the prompt on the phone (in the following 60 seconds), or
- they stop running/walking for the following 60 seconds (That is, their pace should be less than half of what they were doing between Start and Finish).
After 60 seconds, they will hear the normal beep for a punch of Finish. Their time will be recorded as the time they first approached the finish.
With “Confirmed Finish” the only ways in which an “accidental punch of Finish” can occur are:
- all controls have been visited (so it’s probably not “accidental”), or
- the time in a Score event is past 90% of the allowed time (or overdue), or
- the user taps the Confirm button after an unintended visit to the Finish, or
- the user does not respond to the prompt to Confirm/Cancel within 60 seconds and slows/stops in that period.
If a participant accidentally visits the Finish, do they need to take any action when they hear 4 Chimes?
- If they don’t want to Finish, they can keep walking/running at about the same pace as they were previously and the interim punch of Finish will be cancelled at the next control (or after 60 seconds). They need to visit at least one control before coming back to Finish.
- Otherwise, if convenient, they can tap the “Cancel” button on the phone.
- As always, we recommend that unless they are carrying your phone in their hand, that they blank the screen to avoid any accidental input to the phone.
Flowchart
For those people who would like to see the logic of Confirmed Finish in a flowchart:
