Register | Login
Attackpoint - performance and training tools for orienteering athletes

Training Log Archive: Psuba

In the 1 days ending Oct 8, 2017:

activity # timemileskm+m
  Orienteering1 1:27:02 6.7(13:00) 10.78(8:05) 6930 /30c100%
  Running1 3:23 0.43(7:58) 0.68(4:57) 16
  Total1 1:30:25 7.12(12:42) 11.46(7:53) 8630 /30c100%

» now

Sunday Oct 8, 2017 #

10 AM

Running warm up/down 3:23 intensity: (10 @1) + (22 @2) + (1:12 @3) + (1:39 @4) 0.68 km (4:57 / km) +16m 4:25 / km
ahr:142 max:161 shoes: VJ iRock 2016

Orienteering race (Brown) 1:27:02 intensity: (5 @1) + (7 @2) + (1:06 @3) + (29:26 @4) + (56:18 @5) *** 10.78 km (8:05 / km) +69m 7:49 / km
ahr:167 max:180 spiked:30/30c shoes: VJ iRock 2016

SARUM Galoppen, Foxbury plantation.

Given my shape I considered this a training exercise and just wanted to see how my shape holds up through a full brown course (was even tempted to just run blue but decided that would be too much chickening out).

Lovely weather at least but the area was very boggy anyway so wasn't surprised that it felt less than glorious. Mostly tough going when not taking the roads and I mostly didn't - as I ran early that meant making the elephant tracks and getting bogged down, losing a lot of time from people running later or taking routes around. That's due to not only running early and having to bash through bracken but also generally not being very good in terrain anyways, so in a strange way it was good practice, although should be doing more purposeful training in that because it clearly holds me down losing much more time to the guys in the front than running on open terrain, so lots to improve here.

If I was going to use this as a proper race then one could say I was consistently choosing the wrong routes, but this wasn't about trying to get any result.

Some fairly clear mapping issues, but they mostly didin't contribute to the few navigational mistakes, just contributed to wrong routes or slower running. Fairly sure that #11 was much further SW than mapped.
Otherwise lost time on a few bingo controls.
1:50 on #1
~ 2:20 by going through bracken to #7, it was also unclear as the map marked a veg boundary but it wasn't a clear boundary in reality so bit of faffing about near the control
~0:30 on #8 as I didn't fit the map to the terrain properly, (or was the map not quite representative???) so ran to the left of control
~0:30 bogged down towards #18 trying to get out to the track before the control as the map marked it as rough open - where I had to turn back and track the fence instead it was so horrible (I suspect this was one of the controls where the fast guys could just run around on the track for 85% of the route hence me losing 2 min to the best split)
Huge amounts going to #21 through everything - I guess the good news is I held the direction pretty well which is good, of course lost a lot of time just due to the undergrowth etc.
... which does not explain why I lost confidence in my (good) direction about 25m before reaching #23 and ended up on a loop that cost me about 15-20s
#24 is interesting as I had a good plan out of TG's book (ran to the copse which was visible then to the control site which in turn was visible from the copse) but it probably was unnecessary as the control site was real obvious and so, in turn, it took longer than just running on a bearing.
#25 chose the wrong track (longer) to run on, lost at least 0:30 just on that, maybe more. This is really an error in judgement, not like the run through/run around choices earlier where I could just train running on bearing/terrain run.
about 0:50 on #26 where I ran all the way to the trees and had to make sense of where everything is as the bracken was so high you could not run directly (or I was running too far).

Well, this gets autumn training on its way, I just hope I stay healthy and injury free now. I suspect the autumn season is gone from a competitive perspective but hopefully I can build up an OK 2018 season.

« Earlier | Later »