Parameter-based Scoring - ScoreP
For predefined scoring schemes see: Scoring Schemes
The page describes defining customised scoring schemes using a set of parameters. This is meant for use by experienced MapRun Administrators.
The page describes defining customised scoring schemes using a set of parameters. This is meant for use by experienced MapRun Administrators.
ScoreP introduces the ability to define scoring schemes based on a set of parameters rather than using one of the predefined schemes like ScoreQ, ScoreM.
ScoreP is only available in MapRun6 (and MapRunG on Garmin). It will NOT work in the old MapRun App nor the MapRunF App.
To set a ScoreP event:
It is recommended that if the local scoring scheme is not well-known to local participants, a descriptive text or table be provided on the printed map. Unfortunately, the set of parameters themselves, do not provide a simple clear explanation to a runner of what score they would get for each control.
Also, we have ScoreB and ScoreW, which we’ve called scoring schemes they are actually rules for the event as well as scores. ScoreB defines rules regarding Odds and Evens, and ScoreW defines rules about special control punches only available in a specific time window.
ScoreP allows the organiser to use the “Rules” of ScoreB or ScoreW and define their own scoring, but it doesn’t allow the defining of new “Rules”. The way this works is that “Rules” are applied in preparing the list of valid punches which is then scored. Only punches that meet the rules are included in the results table that is scored.
The rules settings can be: N – normal (or no special rules – a “standard” score event)
B – ScoreB rules
W – ScoreW rules
Warning: ScoreB and ScoreW rules have not been implemented in the initial release of ScoreP. ScoreP cannot be combined with the MX code for a "Mass Start".
ScoreP also works with the “ShowMe” function that is introduced in MapRun6. This is where the organiser allows the runners to view their location on the screen a certain number of times during their run. ScoreA allows a “cost” or “penalty” to be applied to a runners use of this function. For example lose 10 points for each use of “ShowMe”.
ScoreP is defined by a string of parameters similar to the following:
N, 0, 1.0, 10, 1.0, 0, 0, MRU, 30.0, 9.0
Where each parameter is listed in order below, with the values that apply to the existing pre-defined scoring schemes
ScoreP is only available in MapRun6 (and MapRunG on Garmin). It will NOT work in the old MapRun App nor the MapRunF App.
To set a ScoreP event:
- Set the score type to ScoreP (in the filename/settings)
- In settings – Include the set of parameters as a string like: “N, 0, 1.0, 10, 1.0, 0, 0, MRU, 30.0, 9.0”
- The score for each control, the total score and any penalty are all Integer values (not floating point numbers).
It is recommended that if the local scoring scheme is not well-known to local participants, a descriptive text or table be provided on the printed map. Unfortunately, the set of parameters themselves, do not provide a simple clear explanation to a runner of what score they would get for each control.
Also, we have ScoreB and ScoreW, which we’ve called scoring schemes they are actually rules for the event as well as scores. ScoreB defines rules regarding Odds and Evens, and ScoreW defines rules about special control punches only available in a specific time window.
ScoreP allows the organiser to use the “Rules” of ScoreB or ScoreW and define their own scoring, but it doesn’t allow the defining of new “Rules”. The way this works is that “Rules” are applied in preparing the list of valid punches which is then scored. Only punches that meet the rules are included in the results table that is scored.
The rules settings can be: N – normal (or no special rules – a “standard” score event)
B – ScoreB rules
W – ScoreW rules
Warning: ScoreB and ScoreW rules have not been implemented in the initial release of ScoreP. ScoreP cannot be combined with the MX code for a "Mass Start".
ScoreP also works with the “ShowMe” function that is introduced in MapRun6. This is where the organiser allows the runners to view their location on the screen a certain number of times during their run. ScoreA allows a “cost” or “penalty” to be applied to a runners use of this function. For example lose 10 points for each use of “ShowMe”.
ScoreP is defined by a string of parameters similar to the following:
N, 0, 1.0, 10, 1.0, 0, 0, MRU, 30.0, 9.0
Where each parameter is listed in order below, with the values that apply to the existing pre-defined scoring schemes
Anomalies:
Please note the following anomalies/bugs:
- If you use SEC as the TimeBaseSelector, runners get a "NEGATIVE PENALTY" for finishing early (ie a BONUS)
- The FixedScorePerControl value is also applied to Start and Finish. This doesn't affect the ranking of runners as everyone need to visit S1 and F1 for a valid run.
Note that if a floating point value is entered where an integer is required, it will be rounded to an integer value. eg a FixedScorePerControl of 20.2 will be rounded to 20.
A recommended approach to defining a new scoring scheme is to start with the parameters shown below for a predefined Scoring scheme that is close to what you want, and then fine-tune the parameters.
For example to use ScoreP to define a typical Rogaining scoring scheme, which is like ScoreQ except that the time penalty is 10.0 points per minute rounded up, instead of 30.0 points, start with ScoreQ:
N, 0, 1.0, 10, 1.0, 0, 0, MRU, 30.0, 9.0 and replace the “30.0” with “10.0”
Or for 0.5 points per second late, replace “MRU, 30.0” with “SEC, 0.5”
Caution
There is plenty of opportunity to mess this up completely, so please take care with using ScoreP. Test your scoring scheme thoroughly before using it.
To that end, the MapRun Console has a Scoring Simulator that allows Administrator to:
Enter the score parameters
AND
A hypothetical runners result (list of punches, time over the time limit, number of uses of “ShowMe”)
TO
Calculate the resulting score
Please only ask for support on ScoreP, after you can show that the score produced by MapRun6 for a runner in an event is different from that produced by the Scoring Simulator (using the same data).
Please note the following anomalies/bugs:
- If you use SEC as the TimeBaseSelector, runners get a "NEGATIVE PENALTY" for finishing early (ie a BONUS)
- The FixedScorePerControl value is also applied to Start and Finish. This doesn't affect the ranking of runners as everyone need to visit S1 and F1 for a valid run.
Note that if a floating point value is entered where an integer is required, it will be rounded to an integer value. eg a FixedScorePerControl of 20.2 will be rounded to 20.
A recommended approach to defining a new scoring scheme is to start with the parameters shown below for a predefined Scoring scheme that is close to what you want, and then fine-tune the parameters.
For example to use ScoreP to define a typical Rogaining scoring scheme, which is like ScoreQ except that the time penalty is 10.0 points per minute rounded up, instead of 30.0 points, start with ScoreQ:
N, 0, 1.0, 10, 1.0, 0, 0, MRU, 30.0, 9.0 and replace the “30.0” with “10.0”
Or for 0.5 points per second late, replace “MRU, 30.0” with “SEC, 0.5”
Caution
There is plenty of opportunity to mess this up completely, so please take care with using ScoreP. Test your scoring scheme thoroughly before using it.
To that end, the MapRun Console has a Scoring Simulator that allows Administrator to:
Enter the score parameters
AND
A hypothetical runners result (list of punches, time over the time limit, number of uses of “ShowMe”)
TO
Calculate the resulting score
Please only ask for support on ScoreP, after you can show that the score produced by MapRun6 for a runner in an event is different from that produced by the Scoring Simulator (using the same data).