I am looking at setting up a true Trail Orienteering event.
For regular orienteering events I would use sportident and OE or oEvent to run the controls / timing.
A requirement for Trail Orienteering is a timing system that does not allow punching additional controls.
Is there an obvious way to do this in OE or oEvent?
IE. mp / or penalty for competitors who punch codes that are not listed on their course (even if they have also collected the correct codes in order).
I'm sure there is a complete guide out there but haven't yet found it...!
That's easy, with any epunch system:
Just print out the full list of controls, and use that to detect any additional punches.
If you want to be more fancy then you write your own sw to process the raw epunch system dumps, i.e. like we did in order to handle the peculiar requirements for the kids' group race during O-Festivalen: They had a score-O with some controls that had to be taken in a specific order, bonus points for best split on one or two legs (that then had to be visited in that order), and deductions for running over the time limit.
The final perl code was just a page or two afair.
just to confirm - OE does not have a method of penalising additional controls. In the OE-score variant, you could define massive penalty points for the surplus controls, but sadly, the points are defined on a per-control basis only, so it would affect all athletes, there could be no courses that actually should use that control.
So, summary - OE isn't going to work for you.
Of course, if a given control is actually kind of a trap, meaning nobody at all should use that control, you could program the station to be a "clear" box :)
One option is to use MeOS. I haven't done it but I gather it includes some tools so that you can easily write custom results calculation setups. Sounds like that could get you exactly what you want.
SportIdent has been used for a number of Trail-Os in Europe, including WTOC. I'm not sure what software they're using, though. You might try contacting Martin Fredholm from the IOF Trail-O committee.
It should probably use more of a score-O system where certain controls earn a point and others are worth zero. But with checking on order punched (if you care) and making sure they haven't punched more than one at each control site.