Training Log Archive: oxensdIn the 7 days ending Nov 11, 2017:
| ||||||||||||||||||||||||||||||||||||||||
| « | » |
| » now | ||||||||||
| |||||||||||||
| Su | Mo | Tu | We | Th | Fr | Sa | |||||||
Sunday Nov 5, 2017 #
Event: DVOA Mount Penn - Antietam
10 AM
Orienteering race (11.75km - 8.40 min/km) 1:38:41 [4] 9.5 km (10:23 / km) +275m 9:04 / km
DVOA 50th Anniversary race at Mt Penn, Reading PA. Long, ran red and glad I did as this was a really enjoyable and fast race. Competed in M45 but in hindsight should have signed up for M35 as the only other runner there was JJ who mispunched! Placed 14 out of 23 finishers, but pretty happy with my running pace which was one of the best all year. Weather conditions were perfect, about 50, some fog, tiny drizzle.
Started out with a silly mistake to #1, lack of concentration and rushed it. Looking at GPS I ran too far on the path before cutting in, had intended to cut from the second intersection with the small rock. Then ended up on a larger path and got confused, at first assumed I must be further down on the path from the control. 3 silly minutes.
#2 was fine. #3, tried to read the boulder field and the green but it didn't add up, ended up too far down and had to go back up. 1 minute. #4 through #6 were fine.
#7 was an interesting route choice, I had intended to take the path half way up the hill and go slightly north. But I missed the path (covered with lots of leaves presumably) and decided to follow contour lines and go straight. This worked well and looking at splits may have been the best route choice, I did better on this leg than most compared to the
#8-#9 went well, then #10 presented another good route choice. I took one look at the climb going straight and the complex paths, and instead decided to go down the hill and run on paths the entire way. About 200m longer, but 20m less climb and much less complex navigation. Ted told me afterwards that going east following the contour lines - the other route I considered - lost him several minutes due to the rough terrain.
#11 was interesting, the approach was in a dense maze of MBT tracks, "corn field style", with limited visibility. I tried to follow the paths which went OK but in the end got lucky and saw the control 20m away.
#12-#14, by this time I had decided to ignore the complex paths and just go straight, since the terrain was nice and open (if rocky). Worked well, I slightly overshot #14 but only 10s lost.
#15 was another route choice, the initial path through the green was probably the only sensible way in the beginning (I didn't trust the power line, can be slow), but once out of the green there was a clear choice between going W on the nice paths or straight through. The path was so nice and inviting that I did that, even though there was an extra 10m climb or so. I think it was the best route, but then I managed to screw it up by thinking I was going to #18 instead of #15 (tired brain), and then compounded it by following the path down the hill past 18 which lost me 20m altitude. Probably cost me 2min, although attackpoint didn't register that.
#16-#19 were fine, I was getting tired after #17 so slow slog up the hill. Approaching #20 I somehow went down too low (tired brain again, I thought I was keeping altitude), ended p on the path and lost 1min.
#21 last control, in hindsight taking the right path was probably faster.
Very enjoyable race!
Map and GPS track here:
https://s3.amazonaws.com/oxensnas/Archive/Archive/...
Started out with a silly mistake to #1, lack of concentration and rushed it. Looking at GPS I ran too far on the path before cutting in, had intended to cut from the second intersection with the small rock. Then ended up on a larger path and got confused, at first assumed I must be further down on the path from the control. 3 silly minutes.
#2 was fine. #3, tried to read the boulder field and the green but it didn't add up, ended up too far down and had to go back up. 1 minute. #4 through #6 were fine.
#7 was an interesting route choice, I had intended to take the path half way up the hill and go slightly north. But I missed the path (covered with lots of leaves presumably) and decided to follow contour lines and go straight. This worked well and looking at splits may have been the best route choice, I did better on this leg than most compared to the
#8-#9 went well, then #10 presented another good route choice. I took one look at the climb going straight and the complex paths, and instead decided to go down the hill and run on paths the entire way. About 200m longer, but 20m less climb and much less complex navigation. Ted told me afterwards that going east following the contour lines - the other route I considered - lost him several minutes due to the rough terrain.
#11 was interesting, the approach was in a dense maze of MBT tracks, "corn field style", with limited visibility. I tried to follow the paths which went OK but in the end got lucky and saw the control 20m away.
#12-#14, by this time I had decided to ignore the complex paths and just go straight, since the terrain was nice and open (if rocky). Worked well, I slightly overshot #14 but only 10s lost.
#15 was another route choice, the initial path through the green was probably the only sensible way in the beginning (I didn't trust the power line, can be slow), but once out of the green there was a clear choice between going W on the nice paths or straight through. The path was so nice and inviting that I did that, even though there was an extra 10m climb or so. I think it was the best route, but then I managed to screw it up by thinking I was going to #18 instead of #15 (tired brain), and then compounded it by following the path down the hill past 18 which lost me 20m altitude. Probably cost me 2min, although attackpoint didn't register that.
#16-#19 were fine, I was getting tired after #17 so slow slog up the hill. Approaching #20 I somehow went down too low (tired brain again, I thought I was keeping altitude), ended p on the path and lost 1min.
#21 last control, in hindsight taking the right path was probably faster.
Very enjoyable race!
Map and GPS track here:
https://s3.amazonaws.com/oxensnas/Archive/Archive/...
C • ty 1