Register | Login
Attackpoint AR - performance and training tools for adventure athletes

Training Log Archive: Anvil

In the 1 days ending Apr 30, 2011:

activity # timemileskm+m
  Orienteering2 1:01:58 4.47(13:51) 7.2(8:36) 293
  Total2 1:01:58 4.47(13:51) 7.2(8:36) 293

«»
1:01
0:00
» now
Sa

Saturday Apr 30, 2011 #

9 AM

Orienteering race 44:39 intensity: (11 @2) + (16 @3) + (3:45 @4) + (40:27 @5) 4.7 km (9:30 / km) +200m 7:50 / km
ahr:175 max:183 shoes: Inov8 Oroc 280

West Point Middle.
Very physically tough middle course. A very rusty, mediocre run - only spiked 8 of 16 controls. Also forgot control description holder, so quite a few small errors in the circle. Map. Map/Video Combo.

S-1: Didn't realise the start punch was the start, so ran 15 secs along the trail before I realise something was up. Then in a rush, don't orient the map properly and head up towards the much smaller hill to the SE of the hill I'm meant to head up. It didn't help there was an unmapped rockface on the smaller hill right where there was meant to be on the larger one - but I do remember thinking, 'wow, this hill is really easy to climb for so many contours....' roughly 45 secs wasted, straight off the bat.
2: Straightforward. Contour up to the broad gully and over the plateau. Was tempted to drift west on the plateau, but the detail kept me on track. Flag was higher in the gully than expected. Spike.
3: Got a lucky glimpse of the flag as I crested the hill. It disappeared from sight, but stayed confident and spiked it.
4: Planned to go south around the marsh. Bad exit direction meant I should have changed my tune and gone north, but was pigheaded about sticking to my plan. Never saw the north road option which was clearly the fastest. ~45 secs lost on both sub-optimal route and poor execution.
5: Contour to the road, then rough compass due north. Spike.
6: Starting to feel very tired already, maybe started too hard after initial mistake. Lost contact rounding the hill and nothing seemed to make sense, just kind of bumbled along each knoll till the flag appeared.
7: Hesitant again. Knew I had to drop a contour but really had to force myself to do so.
8: Physically tough leg. Diagonal uphill through waist high scrub. Obvious attackpoint meant it was just a long slog. If you'd told me I was at Honeysuckle Creek at this point I would have believed you. Spike.
9: Plan was to go below the rockline in the gully and climb up at the last minute. Not the best plan, but still a plan. The gully was filled with new deadfall and other crap, so climbed up early to find more crap. I get to the knolls in the northwest of the circle. There's a guy standing on the feature I think is the right one, but he's not moving and looking around, so I figure it can't be there. After 15 secs of looking at the map trying to work out where I am, he leisurely walks off the rock and punches the control next to it.
As I run in and punch he offers a slightly obnoxious, 'you're welcome'.
10: OK. Used the green to guide me in. Wasn't totally sure that the boulder was right till I saw the flag - it seemed a bit small and the shape of the land didn't really fit the contour to me. Spike.
11: Contour to the saddle then down the gully. Cautious since I didn't want to make a parallel error. Screwed up in the circle, misread the feature.
12: Down the gully then a slog up the hill. Picked up the big double boulder attackpoint but misread the clearing to the south. Was standing 20m away from the flag mildly panicing before I noticed I was at a second small gully to the north.
13: Round the hill and straight in. Was a little high to begin with but the pond pulled me in. Again screwed the circle as I was looking for a boulder.
14: Biggest error of the race. Like many others, stopped short on #81. Just could not locate that feature on the map (was looking for a cliff with tick lines, not a rockface), took a very long time to relocate and make my way into the circle. ~3:00.
15: Easy, dropped a little too much and had to climb. Lost motivation. Spike.
16: Straight forward, but liked I still had to read the map going to the final control. Spike.
1 PM

Orienteering race 17:19 intensity: (6 @1) + (13 @2) + (8 @3) + (3:55 @4) + (12:57 @5) 2.5 km (6:56 / km) +93m 5:50 / km
ahr:177 max:187 shoes: Inov8 Oroc 280

Sprint Race at West Point. Map

Warmed up better for this race and felt much better for the whole thing.
Race went as planned, strong and smooth race except for the spectator control.

S-6: No problems. A little trouble getting into the new scale at #1 and a bit hesitant on the steep slopes at #3 and #6.
#7: Got a little confused when I never picked up the trail out of #6. Decided just to ignore it and use the contours..
#8-11: No real mistakes, but generally sloppy on the micro routes on these legs - on each of these I climbed one or two contours more that was necessary. Looking at the results, this is the only section of the course where my splits are consistently slower than Ross and Robbies.
#12-13: Fine, tried to stay strong on the climb.
#14: The big one. Lost contact and stopped way too early - lost 35secs. Amateur hour.
A couple people mentioned that being an early starter, I didn't have the benefit of seeing the 'flow' of the spectator control so the mistake is more acceptable - but I figure I still had a map in my hand telling me where to go, so I can't really use that to justify that mistake. Also had the fastest split on the following leg out of the spectator control and I never saw anyone doing that one as well.
#15-17: Good. Flowed well and spiked all 3. Probably too well, since my SI never registered #16.
#18: Weak Aussie route. Dropped to the road to avoid the light green. Lost 5 secs to the leaders on this misdemeanor.

Looking at the results now, there's a lot of opportunities to gain more time out there that aren't connected to running speed. I don't have a lot of experience in forest sprints, so it's good to have things to work on.

Regarding #16 - I know I went to it, GPS confirms it, so the unit just must have been sleepy.
Missing out on 3rd place to a SI fail does sting a little, but I figure in over 10 years of use this is the first time it has failed me. I'll just have to make sure I listen for the beep in the future.

« Earlier | Later »