My club uses "Odds and Evens" Score quite often for low key events - it makes best use of A4 size maps at 1:5,000 for us. I had a problem when trialling ScoreB with MapRun in as much as I found myself sometimes collecting 2 x Odds and then passing close enough to register 2 x Evens on the way to my next intended Odd target - this obviously then only allowed me to score 2 x Odds in total! Would there be any chance of implementing an option for the number of controls that have to be collected in one block before moving on to the next? Probably 3 per block as a minimum, but 5 actually seems like a better number to have to collect initially before moving on to block two.
This looks a tricky one. If I'm interpreting this correctly ...
The more controls of the second type you need to visit to make the switch from Odd to Even, the more likely it is you'll accidentally visit one of the type of controls you started with.
E.g. Odd Odd Odd Odd Odd Even [intentional] Even Odd [accidental] Even Even Even
I think if you had to visit 3 to switch, the sequence above would give you 6 Odds and 3 Evens
If you had to visit either 1 or 2 to switch it would give you 5 Odds and 5 Evens (which is what you'd intended in this example)
Presumably if you had to visit 3 to switch but only visited 2 of the new type at the end, you'd still get the credit for those?
E.g. Odd Odd Odd Odd Odd Even Even
would be 5 Odd and 2 Even (even though you hadn't visited enough to switch)?
back again! .... I think the option of 3 consecutive controls is probably about optimum for not messing up (yourself) - an added thing to think about during the event might be the realisation that if you did
odd, odd, odd, even, even, even,
you're then stuck with even and cannot go back to odd! I like 3 - seems like a good compromise number!
An alternate mode for ScoreB didn't make it into the MapRun6 release. ScoreB still works as per the existing arrangement of visiting 2 controls of the opposite set to flip.
Although needing to visit 3 controls of the opposite set has some attraction, I'm still not convinced that it will be better.
I suspect that if you have a course where runners are accidentally visiting two controls in sequence of he second set whilst, running the first set, then in changing to needing 3 controls to flip, they will similarly likely accidentally visit one of the first set while trying to visit 3 in sequence of the second. .. so the flip won't occur.
I think there are some options:
- Run with ScoreB and then in the Console adjust/correct any scores where there was an accidental flip/not-flip
- Run with ScoreQ (or V is you want ScoreV scoring), and tell people the rules and then manually check/adjust (again in the Console).
- Also you can export the event results file (.csv) and re-score it using whatever logic you like... and then publish a new result table on the Club Website.