Training Log Archive: MJChildsIn the 7 days ending Sep 16, 2017:
| |||||||||||||||||||||||||||||||||||||||||||||||||||||
| « | » |
| » now | ||||||||||
|
|
| |||||||||||
| Su | Mo | Tu | We | Th | Fr | Sa | |||||||
Saturday Sep 16, 2017 #
Orienteering race 1:20:34 [4] 4.2 km (19:11 / km)
Letchworth Falls Classic Day 1, east side of the gorge. Tough course. Long, too. Lots of diagonal uphill legs. Had a hard time with the 1:7500 scale again. Just can't relate to it.
Had lots of bobbles, starting w #1, but each time, managed to recover near the control within a min or two. So, sloppy but lucky run.
Came upon a bee tree between 9-10. Heard it first--thought it was a vehicle motto. Lots of activity in and out of the tree cavity approximately 8' high. Glad honey bees don't frighten me.
Surprised that I did relatively well on the course overall. Exhausted at the end. Very physical course.
Had fun.
Had lots of bobbles, starting w #1, but each time, managed to recover near the control within a min or two. So, sloppy but lucky run.
Came upon a bee tree between 9-10. Heard it first--thought it was a vehicle motto. Lots of activity in and out of the tree cavity approximately 8' high. Glad honey bees don't frighten me.
Surprised that I did relatively well on the course overall. Exhausted at the end. Very physical course.
Had fun.
Friday Sep 15, 2017 #
Walking 30:00 [2]
The usual w Carl.
Sunday Sep 10, 2017 #
Orienteering race 1:23:17 [4]
Pawtuckaway Camping Weekend Brown Course.
This course started in the woods and ended in the logged areas, so I was focused and determined to have a clean run. I was careful and hit #1-5 with no problems.. At all. Was having a really great run. Then, on #5-6, my efforts were sabbotaged by the course setter. I chose to head S-SW until I hit the trail, I would turn right and fine tune my location, then find an attackpoint into the control about 100 m beyond the trail. The leg was about 300-350 m. Simple, I thought. Problem was, there was an unmarked trail between 5 and 6 which I hit before I hit the only mapped trail. I came upon it sooner than I expected, but thought it was my lapse. Turned right, adjacent features seemed to match, up ahead and to the left I saw a control which I thought was mine and was excited to attack it. Turned out to be the wrong code. Long story short, I looked around then decided to bail out to the trail assuming I had not run along it long enough. Couldn't get the features along the trail to match the map. Headed west and north on the trail and began to wonder if this was the "unmapped trail" that Carl mentioned running across on Saturday. Ran about 400-500 m on the trail before I convinced myself that it must be the unmapped trail. Returned to #5, after encountering Mariama, and enroute, found where the unmarked trail met the marked trail. Bummer. Once at #5, I took a bearing and checked off features on the way to #6.
This did not have to happen. The master maps could have been marked with the trail, even with questionable location, just so competitors would know to expect another trail.
Yes, this was just a B or C event, but why ruin runs for many people involved when a simple fix could have been provided.
Otherwise, it was fun to be in the forest, except for the logged areas. I guess those areas just feel like the moon to me and I want to be out of them as soon as possible. I hate stark settings, and these have bad mojo.
This course started in the woods and ended in the logged areas, so I was focused and determined to have a clean run. I was careful and hit #1-5 with no problems.. At all. Was having a really great run. Then, on #5-6, my efforts were sabbotaged by the course setter. I chose to head S-SW until I hit the trail, I would turn right and fine tune my location, then find an attackpoint into the control about 100 m beyond the trail. The leg was about 300-350 m. Simple, I thought. Problem was, there was an unmarked trail between 5 and 6 which I hit before I hit the only mapped trail. I came upon it sooner than I expected, but thought it was my lapse. Turned right, adjacent features seemed to match, up ahead and to the left I saw a control which I thought was mine and was excited to attack it. Turned out to be the wrong code. Long story short, I looked around then decided to bail out to the trail assuming I had not run along it long enough. Couldn't get the features along the trail to match the map. Headed west and north on the trail and began to wonder if this was the "unmapped trail" that Carl mentioned running across on Saturday. Ran about 400-500 m on the trail before I convinced myself that it must be the unmapped trail. Returned to #5, after encountering Mariama, and enroute, found where the unmarked trail met the marked trail. Bummer. Once at #5, I took a bearing and checked off features on the way to #6.
This did not have to happen. The master maps could have been marked with the trail, even with questionable location, just so competitors would know to expect another trail.
Yes, this was just a B or C event, but why ruin runs for many people involved when a simple fix could have been provided.
Otherwise, it was fun to be in the forest, except for the logged areas. I guess those areas just feel like the moon to me and I want to be out of them as soon as possible. I hate stark settings, and these have bad mojo.