Training Log Archive: coadyIn the 7 days ending Jun 15, 2013:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| « | » |
| » now | ||||||||||
|
|
| |||||||||||
| Su | Mo | Tu | We | Th | Fr | Sa | |||||||
Thursday Jun 13, 2013 #
11 AM
running (lunch run) 29:00 [3] 5.3 km (5:28 / km)
jog at lunch .. warm up for aqua slower than normal but able to power up all hills
GYM (Aqua) (aqua) 50:00 [3]
Monday Jun 10, 2013 #
10 AM
Orienteering race (QBIII - mid) 50:45 [4] 6.18 km (8:13 / km) +87m 7:40 / km
ahr:154 max:169 shoes: Inov-8 Mudclaw 333
Hit #1 ok cutting some corners through tracks, but came across girl on the easy/very easy course on the track junction who was in tears, she didn't know where she was or which direction to go, now I realise you are not supposed to help anyone on the course but there is no way I was going to do nothing! so I pointed her in the right direction and gave her some words of encouragement.
this left me a little distracted so I played it safe to hit the rockline and turn left
#4 veered left, hit some rock detail and got a little confused decided I had not gone far enough so I would keep going. hit gully with cliff and termite mound losing about 20-30 seconds of second guessing.
#5 and 6 seem familiar from last year,
#7 went high to get some cleaner running
#10 veered left on purpose from the large track but veered too far, found the other mound, should have taken a bearing from the nearer track.
was happy with navigation, but felt like I was very slow running.
RouteGadget
this left me a little distracted so I played it safe to hit the rockline and turn left
#4 veered left, hit some rock detail and got a little confused decided I had not gone far enough so I would keep going. hit gully with cliff and termite mound losing about 20-30 seconds of second guessing.
#5 and 6 seem familiar from last year,
#7 went high to get some cleaner running
#10 veered left on purpose from the large track but veered too far, found the other mound, should have taken a bearing from the nearer track.
was happy with navigation, but felt like I was very slow running.
RouteGadget
Sunday Jun 9, 2013 #
10 AM
Orienteering race (QBIII - long) 1:32:26 [5] 12.3 km (7:31 / km) +230m 6:52 / km
ahr:154 max:172 shoes: Inov-8 Mudclaw 333
splits indicate I lost time at
3 (ran past the second clearing - they seemed to join then over corrected and didn't see the control on the first pass. relocated to track when I realised I had gone too far)
5 (took the right side of the cliff, it looked yellow but I climbed an extra 2 contours, left would have been better, went past the control location but didn't see it, a case where it was more visible further from the control as it didn't occur to me to look 5m above)
7 (was searching for control but then it occurred to me that it was on the bare rock, and I was not searching the rock .. has some people near me from 6 which may have distracted me)
11 (took the track, no mistake, but perhaps could have hit the control in a more direct line in the last bit.)
15 (started to go N but saw a decent "track" to get me out of the fallen timber, so took the left track option which was slow, no nav error but i guess it would have been quicker going N from the control rather than W)
was happy with run apart from #3, a few people within 5 mins but way down on the standings
RouteGadget
3 (ran past the second clearing - they seemed to join then over corrected and didn't see the control on the first pass. relocated to track when I realised I had gone too far)
5 (took the right side of the cliff, it looked yellow but I climbed an extra 2 contours, left would have been better, went past the control location but didn't see it, a case where it was more visible further from the control as it didn't occur to me to look 5m above)
7 (was searching for control but then it occurred to me that it was on the bare rock, and I was not searching the rock .. has some people near me from 6 which may have distracted me)
11 (took the track, no mistake, but perhaps could have hit the control in a more direct line in the last bit.)
15 (started to go N but saw a decent "track" to get me out of the fallen timber, so took the left track option which was slow, no nav error but i guess it would have been quicker going N from the control rather than W)
was happy with run apart from #3, a few people within 5 mins but way down on the standings
RouteGadget