Training Log Archive: TheInvisibleLog

After a detailed perusal of the mistakes I have another lesson from yesterdays orientshow.

Lots of controls within clear view of the start was a good idea. These accounted for 80% of the errors! The much more technically demanding controls hidden up the slope in the granite produced only a few errors, and these errors were sins of omission - middle controls in a line of three that were skipped. My conclusion is that when in full view of spectators, competitors were much more likely to skip the care factor in the interests of seeming to be in control and at speed.

C • mp's 2

RESULTS
I have selected 2 minutes as an appropriate penalty for an error. With this the fastest runners might have chosen to drop one control. Slower runners may have chosen to drop more. No more than 5 errors allowed. This gives 2 variants of the results. Entirely appropriate for this event that hangs on variants.

READ THIS IN 2014
Use Geco software. It will make the results much simpler than OE.

C • Results 18

Two and a half hours mapping, mainly with the purpose of finding my inner introvert after the busy and social day yesterday running the Orientshow. Spent the time on the Crusoe project and the area between No 7 and Crusoe. The good news.. another hour or two and the City of Greater Bendigo Park will be mapped. The bad news.. I was much faster than expected today because this particular area is low in detail.

Terrain run with Julie.

Event: Bendigo Orientshow
 

(NOTE TO SELF READ THIS IN 2014)

LESSONS FROM ORIENTSHOW

1. Sometimes one map change is not enough.
2. Skip the classic race altogether.
3. Try not to use an enlarged 1:15000 map, even of granite.
4. Time penalties for mispunches.
4. Always double check everything about the last control placed in the field.
5. Make the hagaby the longer race, not the orientshow
6 Put a nth rose on the map. It keeps some people happier (and a scale)
7 Forgot this one for the moment
8 Remember to have a pee and a drink sometime during the day.

C • Thanks 13

NOTE FOR SELF WHEN THINKING OF THE NEXT ORIENTSHOW

The final night setting up the event files should be two nights.
1. Download and input the competitors into three event files
2. Allocate hire sticks for those with old sticks
3. Seed the competitors
4. Seed the variations.
5. Match the competitors with variants.
6. Place maps in plastic bags with hires sticks so that variant, name and stick number match the OE file.

So set the closing date on the Tuesday.

C • Closing date 4

Placing orientshow controls which took over 5 hours. Saturday morning may well have other commitments. Now a night spent building the event files.

After placing the controls, the run. Up the West spur and along to the summit. Then down the south face and traverse along beneath the Spurloin cliff line (climbers will know what I refer to, for the rest, its the big slabs on the south-west of the mountain). I think it would be pretty tough as orienteering terrain across the steepest part of the face. But below the steep face there is good terrain, about a square kilometre. Given the orientshow is happening in a fifth of that area, I foresee some more mapping in retirement (retirement date being anything from 4 months to three years time depending upon matter beyond my control). It may be the only time I ever get to use traditional analog photogrammetry (left over from mapping the north of the mount). After that the temptation will be to link with the rest of the map. The east and west sides provide good connections of reasonable terrain.

Roller pain... but it seems to work.