Software
Analysis graphs for score courses
On a score course every competitor picks their own controls in their own order, so the usual split graphs have nothing to compare. meshO Manager's spectator site and kiosk now have a set of graphs made for score courses: which controls paid, which routes the leaders took, how the field spent its time, and who came back late.
After a line course, the conversation at the finish is about splits: where you lost time, and who was fastest between 7 and 8. After a score course it’s a different conversation. Which controls did you get? Was 35 worth going out for? Did you make it back in time?
meshO Manager’s analysis graphs used to have nothing to say about that. Every one of them compares legs, and on a score course nobody runs the same legs. Now a score course gets its own set of graphs, sixteen of them, on the spectator site that competitors open on their phones and on the kiosk at the arena.
Every picture here is from the sample score event that comes with Manager: six classes of 100 competitors on one 45-minute course of 30 controls, worth 10 to 50 points each, with 10 points off for every minute late. You can add it from Try a sample event on the Events page and look at every graph yourself.
Which controls paid?
Control popularity counts how many competitors visited each control, shaded by what it was worth. The darkest bars are the 50-pointers.
Points against popularity puts the same numbers on two axes: what a control was worth across, and the share of the field that visited it up. A control high on the left was cheap but everybody went anyway, because it was on the way. A control low on the right was dear and out of reach.
What the leaders took compares the top tenth of the field with everyone else, control by control. Here 33, 34 and 32, the 50- and 40-pointers along the top of the map, were visited by 50 to 60 percentage points more of the leaders than of everyone else. That’s the race in one picture: the winners went north.
Which way did they go?
Busiest legs draws every leg anybody ran over the course in purple, with each control’s points inside its circle. The more competitors ran a leg, the thicker its line. Show direction splits each leg into the ways it was run, with two barbs pointing the way.
Route families groups competitors by the part of the course they left out, and names each group after its best competitor. “Like Simon Keller” is the most common way round the course; “Like Daniel Turnbull” is the winner’s, chosen by far fewer people, and it scored more.
Routes in order has a row for each competitor: their controls in the order they took them against the clock, a bigger dot for a dearer control, their total beside their name, and the time limit as a dotted line.
How did they spend their 45 minutes?
Points over time draws each picked competitor’s score climbing as they punch, with the limit marked. The leaders are level for half an hour; the race is decided in the last ten minutes. Points by time block shows the same in ten-minute blocks.
Points against race time and Points against distance put the whole field on one graph, with the picked competitors named. Distance is straight lines between the controls, so it isn’t the distance anybody ran, but it shows who scored a lot without going far. Leg pace shows how long each leg took for its length.
When controls were visited is a grid: controls across, ten-minute blocks down, the number of visits in each square. It shows the field fanning out: the controls near the start are busy in the first ten minutes, and the far ones fill up later.
Who came back late?
Finishing against the limit shows how close to 45 minutes the field came back. Blue is time to spare; red is late, and losing points. Here 56 of the 600 were over.
Points lost to lateness shows the ten competitors the penalty cost most, with what they collected and what it took off them. Niklas Foster collected 440 points and was back at 52:24: eight minutes late, 80 points gone. This graph only appears when somebody was late.
And when more than one class runs the course, Points by class shows the spread of scores in each.
On a phone
The graphs are on the spectator site as well as the kiosk, so a competitor can open them on their phone at the finish. Competitors picks who the graphs about individuals show, the top five to start with. Tap a name in a graph’s key to pick that competitor out.
What you need
Nothing to turn on. Make a score course in Manager as usual, and the analysis page shows these graphs for it in place of the line-course ones.
Routes on the map, Points against distance and Leg pace need a position for the start, the finish and every control, from a Purple Pen import or controls placed on the event map. Without them those three are left out and Leg times is offered in their place, and Busiest legs becomes a ranked list of legs instead of lines over the course. Finishing against the limit needs a time limit.
The score graphs are in the next release of meshO Manager. To read what each one shows, see Score courses in the meshO Manager docs.

