I'm brilliant I never mispunch

[DaveK]

Mmmm, do I have to say? Mispunched both days at the World Masters in Australia a couple of years ago. Thought I might have been more careful after doing so in the first 'qualifying' race! Long way to go to 'mp' twice, enjoyable as it was. Have done it a couple of times since as well. Note to oneself 'always, always, check the control code.'

[HOCOLITE]

Having coached juniors- white and yellow and created a number of exercises to assist in this training I'd like to say I always check the code but I can still remember back as far as yestrday and I know there were two cases when I didn't check- well at least no before I'd punched. I certainly have splits with extra controls in, but most of my (not too many mispunches) are due to brain fade... No 6-9 or using a different crossing point. in the old days having my control card upside down so reading wrong code whilst stood at right control. I think I move slow enough that I can check the control codes sometimes there is great relief thast it says the right number.

[Wayward-O]

I fall into the 'slower' class and have plenty of time to check numbers, but have mp'd on a number of occasions for various reasons:

Once so relieved at finally finding control, I checked the map and ran off without punching. Another time, the course had three controls in a line and I completely ignored the middle one! Yet another time with three controls in a straight line I arrived at the second, decided that I was at the third of the line, and ran off in completely the wrong direction, getting myself totally confused.

On occasion I punch controls knowing that they're not mine (especially when the event will be on routegadget) so that I can see where I actually got to.

[SeanC]

Unregistered punches are a particular problem for me at SI events where b*****s (no apologies for the abusive language, I feel it is appropriate here) stick labels over the flashing light, happy that they hear well and will detect the bleep.

After one of our members made a similar comment a few weeks back, we've taken all the sticky labels off ours now Ian (if you were referring to us). Cock up rather than deliberate I can assure you.

It's an interesting point worthy of a letter to Compass Sport maybe? Do controllers, organisers and planners check this?

[IanD]

After one of our members made a similar comment a few weeks back, we've taken all the sticky labels off ours now Ian (if you were referring to us). Cock up rather than deliberate I can assure you.

It's an interesting point worthy of a letter to Compass Sport maybe? Do controllers, organisers and planners check this?

Glad to hear that DFOK have removed the offending labels.

I wasn't referring to DFOK in particular, although I did once successfully appeal against disqualification at a DFOK event where I had visited a control and the punch didn't register, but the light was covered.

I have in the past written to CompassSport (and the letter was printed), and I have submitted a formal written complaint at a JK - not wanting a course voided, but hoping that the message would get through to the annual major events organisers/planners/controllers conference.

Nevertheless, in answer to your question, it is clear that many controllers and planners do not check that the lights on SI units are visible (wouldn't expect an organiser to check 'in the forest' equipment),

[harry]

One of the best sprint runners in my club and the best Kiwi at WOC ever in all 3 individual disciplines told me he never checks his codes in sprint races. "Things happen too fast, you have to be ready with the next exit route and as long as you are in control of your orienteering you shouldn't need to check your code".

It's definitely a controversial strategy but in sprint the margins are small and there is a lot to keep on top of. Once in a European Champs sprint qualifier I wasn't sure if my last control punch had registered so I went back to the last control, that cost me 5-10 seconds and I missed qualifying for the final by 1 second. It's very likely it did register 1st time, it was emit and I just hadn't quite got the brick in right but usually that registers OK.

[Gnitworp]

One of the best sprint runners in my club and the best Kiwi at WOC ever in all 3 individual disciplines told me he never checks his codes in sprint races.

Certainly a calculated risk worth taking if you win by one second, I'd have thought. The sites in sprint races are, after all, often pretty unequivocal.

[harry]

Agreed. I experimented with not checking my codes in sprints after he told me that. results got better, better feeling with the map (since you have slightly more time) and no DSQs to report yet. Sometimes you definitely have to check the description though! The guy in question says he almost never checks the code and only checks the description if he can't understand the exact location / get the total circle picture from the map.

[Gnitworp]

he .......only checks the description if he can't understand the exact location / get the total circle picture from the map.

and even having to do that is an unfortunate necessity interfering with the real business of orienteering and flow.

[ba-ba]

A certain JWOC runner misspunched at Tyrella as he was only checking the last digit of his codes.
At the moment I remember the last 2 digits of the code for the next 2 (sometimes 3) codes in all forms of O. Reciting the numbers keeps some form of focus (keeps annoying songs out of my head too!)

[maprun]

I remember my first mispunch. Way back in 1973, I was unaware that my control had been ripped off my O top. I punched my map for the rest of the course and was lying in second place in the Southern Junior Champs. I informed the finish team and expected to be disqualified. However, I was later told the controller a certain famous and forbidding Chris Brasher wanted to see me with my map. He reinstated me, based more on a direct question and eye contact, "had I punched at all the controls?" rather than any checking of the punch marks. He gave me some advice, particularly about protecting and securing my card. At 16 I was old enough to appreciate the gesture and advice and learn from it. Like many juniors at the time I had been orienteering for just over a year and had to learn from others who often only had a couple more years experience.

[Kitch]

once upon a time, a long time ago
control descriptions would be published ahead of the race.
Car journeys could be spent memorizing the whole description list.

[graeme]

Not even that long ago, controllers had discretion to reinstate anyone who they were sure had visited the control. I did it quite regularly, particularly where some fault attached to the organisers and no time was gained. e.g.

Competitor finds tag with correct number in adjacent reentrant, but no control.
Competitor fails to use pin punch at a control which some people can't get to work.
At a map exchange (I'd only do this in small events).

I seldom check control codes in Scotland.

[AndyC]

I seldom check control codes in Scotland.

What even when you're controlling?

[IanD]

Not even that long ago, controllers had discretion to reinstate anyone who they were sure had visited the control. I did it quite regularly, particularly where some fault attached to the organisers and no time was gained. e.g.

Competitor finds tag with correct number in adjacent reentrant, but no control.

Surely in this case, as controller you have only two choices. Re-instate the competitor, or void the course?