Training Log Archive: jfredricksonIn the 1 days ending Nov 2, 2002:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| « | » |
| » now | ||||
| |||||||
| Sa |
Saturday Nov 2, 2002 #
Event: US "Classic" Championships
Stretching/Warmup 30:00 [2]
slept:9.0
Warmup for A-Meet.
Orienteering (Red Course) 1:07:39 [4] 8.43 km (8:01 / km) +395m 6:30 / km
Today was the US Champs. I ran M-20 in order to defend my title. I was a little worried going into the race since I was still recovering from my bout with poisen ivy and hadn't been doing much running. After running last weekend, I knew I would not be in perfect running shape, so my strategy for the weekend was to be as clean as possible. Unfortunately since I wasn't able to do much physical training I also was not able to do any technical training. This meant that I could be pretty out of shape Orienteering wise, but after having a good technical race last weekend, I felt fairly confident that I could run clean race as long as I didn't push too hard.
As it turned out running slower was in fact the best strategy and even though I had close to 5 minutes of error, I still won the day. I only made one mistake due to loss of concentration, so I was pretty happy in that regards. My only mistake as such was at the end of the race when I had an easy attackpoint off of a stream. Unfortunately I lost contact with my map for less than a minute and when I refocused, I was not exactly sure where I was along the stream bed. I knew I wanted to follow a stream junction off to the East, and I saw a steep gourge going off in the right direction. I didn't feel as if I had gone far enough, but I wasn't exactly sure since I hadn't been paying close enough attention. I figured I could either be at the right attackpoint, or a reentrant just before it. I decided that it would be best for me to take the risk and check this reentrant first, since if I was at the right one and kept going I would be worse off than going up too early. As it turned out, I was too early and had to cut across the top of the embankment to the control. Overall I lost about 2 minutes on the control.
Other than that I was very well focused. I still made some other stupid errors, but they were simply due to me getting a little confused. One time I went out of a control at a bad angle, but since I was just trying to hit a road, it didn't matter too much. I was still disturbed by this since I thought I had fixed my compassing problems since buying a new compass. I guess I am still prone to making directional errors.
As it turned out running slower was in fact the best strategy and even though I had close to 5 minutes of error, I still won the day. I only made one mistake due to loss of concentration, so I was pretty happy in that regards. My only mistake as such was at the end of the race when I had an easy attackpoint off of a stream. Unfortunately I lost contact with my map for less than a minute and when I refocused, I was not exactly sure where I was along the stream bed. I knew I wanted to follow a stream junction off to the East, and I saw a steep gourge going off in the right direction. I didn't feel as if I had gone far enough, but I wasn't exactly sure since I hadn't been paying close enough attention. I figured I could either be at the right attackpoint, or a reentrant just before it. I decided that it would be best for me to take the risk and check this reentrant first, since if I was at the right one and kept going I would be worse off than going up too early. As it turned out, I was too early and had to cut across the top of the embankment to the control. Overall I lost about 2 minutes on the control.
Other than that I was very well focused. I still made some other stupid errors, but they were simply due to me getting a little confused. One time I went out of a control at a bad angle, but since I was just trying to hit a road, it didn't matter too much. I was still disturbed by this since I thought I had fixed my compassing problems since buying a new compass. I guess I am still prone to making directional errors.