Training Log Archive: sherpes

How important it is to read the control (checkpoint) identifier number or code? here there were two "go" controls pic.twitter.com/ARNzy7vXJT

— Raccoongaine (@Raccoongaine) April 4, 2016

Great run, hunting down the 27 controls in the Blue course (9.8 km) with time under 2 hours. Unfortunately, have now the distinction of finishing this great run with a mispunch on the very last control, the "go" control.

Route

Flying_Pig_2016_Sunday_Classic_14 Blue - Splits

Event: Crooked Compass Adventure Trek
 

Parallel feature error: believed to found 9, but was 10 instead. Depression in red circle was identical to dep at 10 pic.twitter.com/84YUVsSvyF

— Raccoongaine (@Raccoongaine) April 4, 2016

Well, going from 8 to 9, saw a control and went for it. It was not 9, but 10. Punched in without reading the control ID number, and ran over the spur and then down the reentrant right next to the power line, looking for a control flag, "10" in my mind, and the terrain just looked exactly what my mind was expecting from reading the map. Parallel feature indeed.

What was most intriguing is that in the red-circled area were TWO small depressions (not mapped), just like the ones featured on the map for control 10, and the lower one had a pink ribbon with "OCIN" written on it, and a couple of 3-digit control numbers that were written over with a black ink marker. My guess: the course setter originally placed the ribbon there to denote the location of a checkpoint, but the vetter later disqualified it. (but the ribbon stayed).

Wow... that was intriguing, and scrutinizing the map, saw the potential of parallel feature error, ran back to the last control I punched, and upon reading the control ID, it confirmed in my mind that indeed I committed a parallel feature error.

But going back to why there was a ribbon with "OCIN" written on it. That's what I want to know... what's the true story behind that location? is it a trace of history from the course setter and vettor interplay? How far is my guess?

Route

GPS track on what happened at #FlyingPig Saturday Blue course. Found 10 thinking it was 9, and went looking for 10 pic.twitter.com/YyUiyo0ebx

— Raccoongaine (@Raccoongaine) April 5, 2016

C • Extra tape 1

Flying_Pig_2016_Saturday_Classic_14 Blue - Splits

Event: OCIN Flying Pig XX
 

Psychologically dissuaded by presence of glass bottles and trash (blue x), totally missed the control location pic.twitter.com/SaTVLeozJ0

— Raccoongaine (@Raccoongaine) April 4, 2016

4:37 on the first leg, compared to fastest time of 28 seconds. Not a good way to start a 3-day orienteering meet. Route

Flying_Pig_2016_Friday_Sprint_14 Blue - Splits