Training Log Archive: RLShadowIn the 7 days ending Jul 31, 2011:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| « | » |
| » now | |||||||||||
|
|
|
|
|
| |||||||||
| Mo | Tu | We | Th | Fr | Sa | Su | ||||||||
Sunday Jul 31, 2011 #
Event: 2011 OUSA Convention
9 AM
Orienteering 2:06:53 [4] 5.32 mi (23:51 / mi) +427ft 22:10 / mi
shoes: Montrail Mt Masochist Mar 2011
Day 2, Green Y. I really didn't think I could do worse than yesterday, but I managed to. "I was sucks" to use an expression I've heard on AP. I really don't get this sport. At some point I need to either accept that I'm terrible at it and focus more on something that I'm slightly more competent at like running, or else see what I can do to improve myself, but I'm not certain that's possible (can't teach an old dog new tricks, comes to mind).
I accidentally stopped my Forerunner for a few minutes, so I need to correct the time (which at this point is taken right off of the FR).
My course and route below. A few comments probably coming later. As can be seen from the route, my major downfall controls were #2 and #8. When looking for #8, it looked like I may have once again been barely off the map, but it may be an artifact of the scanner not being quite large enough to scan the whole map. In any event, I was very close to the edge.
I accidentally stopped my Forerunner for a few minutes, so I need to correct the time (which at this point is taken right off of the FR).
My course and route below. A few comments probably coming later. As can be seen from the route, my major downfall controls were #2 and #8. When looking for #8, it looked like I may have once again been barely off the map, but it may be an artifact of the scanner not being quite large enough to scan the whole map. In any event, I was very close to the edge.
 |
| From GPS tracks |
Saturday Jul 30, 2011 #
11 AM
Orienteering 1:56:17 [4] 5.74 mi (20:15 / mi) +276ft 19:23 / mi
spiked:8/10c shoes: Montrail Mt Masochist Mar 2011
Green Y, Day 1.
Two very very bad controls. In one of them, I think I was off the map for a bit. That's how bad that one was.
I counted 8 controls out of 10 as spikes, using my loose definition of a spike, but the 2 non-spikes were really major non-spikes.
My course and route below. The big problem spots were #5 and #8.
No issues with 1, 2, 3, or 4.
From 2 to 3, I had to figure out whether to go around the funny-shaped pond on the left side or right side. I started to go left (when I got to the trail), but only for a bit, because I decided the navigation might be easier going right. Just as I started heading back on the path, to go right, I saw PG come out of the woods, and could tell he was going right also, which made me feel better about my decision to go right. And I actually felt good about him catching me when he did -- he started 4 minutes behind me, and I had fears that he would blow right past me when I was about 5 minutes into my run! As it was, I was 14 minutes into my run, which meant he covered in 10 minutes what I covered in 14 minutes. I have a goal of someday being within 50% of his time, so at that point in the race, I was 40% behind him, not bad (at that point!).
Big problems going to 5. I decided against taking the straight line route, being a bit worried (needlessly, I'm sure) about crossing a marsh which also was green. The problem was, when I started heading towards the control, I wasn't sure exactly where I was. It turned out, from my GPS track, that I was very close to the control on my first approach, but I obviously didn't know it. I wound up somewhat off of south edge of the map, finally decided to find the stream, and after a few more back and forths, found a stone wall near the stream which identified my location. From there I made my way to the control, finally. 26 minutes on something that should have been maybe 8-10 minutes.
No issues with 6 or 7.
Big problems again with 8. I see from the GPS track that I was on the right track at one point, but got pulled to the right for some reason (other orienteers in the area may have been a factor). I finally wound up, to my dismay, on the trail. From there, I found a point where I knew where I was, and took a bearing towards the control. Once again, I was on basically the right track, but got pulled off again. Finally, more through luck than anything, I found it. 23 minutes on what should have been around 10 minutes.
I decided to take the easiest route to #9, even though it was very long. I had had my fill of wandering around in the woods with no idea where I was. This took me 18 minutes; I'm guessing that a well-executed straighter line route would have been 12-14 minutes. I think I over-estimated how difficult a straighter route would have been, and under-estimated how tired I was and how long of a distance I needed to cover on the trails and road. I did a lot less running and a lot more walking than I had expected.
Two very very bad controls. In one of them, I think I was off the map for a bit. That's how bad that one was.
I counted 8 controls out of 10 as spikes, using my loose definition of a spike, but the 2 non-spikes were really major non-spikes.
My course and route below. The big problem spots were #5 and #8.
 |
| From GPS tracks |
No issues with 1, 2, 3, or 4.
From 2 to 3, I had to figure out whether to go around the funny-shaped pond on the left side or right side. I started to go left (when I got to the trail), but only for a bit, because I decided the navigation might be easier going right. Just as I started heading back on the path, to go right, I saw PG come out of the woods, and could tell he was going right also, which made me feel better about my decision to go right. And I actually felt good about him catching me when he did -- he started 4 minutes behind me, and I had fears that he would blow right past me when I was about 5 minutes into my run! As it was, I was 14 minutes into my run, which meant he covered in 10 minutes what I covered in 14 minutes. I have a goal of someday being within 50% of his time, so at that point in the race, I was 40% behind him, not bad (at that point!).
Big problems going to 5. I decided against taking the straight line route, being a bit worried (needlessly, I'm sure) about crossing a marsh which also was green. The problem was, when I started heading towards the control, I wasn't sure exactly where I was. It turned out, from my GPS track, that I was very close to the control on my first approach, but I obviously didn't know it. I wound up somewhat off of south edge of the map, finally decided to find the stream, and after a few more back and forths, found a stone wall near the stream which identified my location. From there I made my way to the control, finally. 26 minutes on something that should have been maybe 8-10 minutes.
No issues with 6 or 7.
Big problems again with 8. I see from the GPS track that I was on the right track at one point, but got pulled to the right for some reason (other orienteers in the area may have been a factor). I finally wound up, to my dismay, on the trail. From there, I found a point where I knew where I was, and took a bearing towards the control. Once again, I was on basically the right track, but got pulled off again. Finally, more through luck than anything, I found it. 23 minutes on what should have been around 10 minutes.
I decided to take the easiest route to #9, even though it was very long. I had had my fill of wandering around in the woods with no idea where I was. This took me 18 minutes; I'm guessing that a well-executed straighter line route would have been 12-14 minutes. I think I over-estimated how difficult a straighter route would have been, and under-estimated how tired I was and how long of a distance I needed to cover on the trails and road. I did a lot less running and a lot more walking than I had expected.
Friday Jul 29, 2011 #
2 PM
Running 27:10 [2] 3.01 mi (9:01 / mi) +4ft 9:01 / mi
max:150 shoes: Asics Gel Nimbus 11
Short run, to try to shake out the rust in my legs and in my rib/shoulder area (still a little bit bothersome from the pickleball injury -- trailsnail can snicker now if she wants to :) ). Probably good thing I did, as I definitely felt the rust in my legs and some soreness in my ribs/shoulders the first mile or so, then things got a little better. But of course, I got very warm too. Dew point of 71 degrees.
Wednesday Jul 27, 2011 #
8 AM
Course setting 31:18 [1] 1.02 mi (30:40 / mi) +90ft 28:18 / mi
shoes: New Balance MT461GO
Streamering some controls for Linda's training session.
Running 38:03 [2] 3.91 mi (9:44 / mi) +78ft 9:34 / mi
shoes: New Balance MT461GO
Hojack Trail run, with trailsnail.
I seem to be recovered enough from my pickleball injury to do at least an easy run like this.
I seem to be recovered enough from my pickleball injury to do at least an easy run like this.
Tuesday Jul 26, 2011 #
9 AM
Walking (Dog walk) 1:07:04 [1] 3.56 mi (18:50 / mi) +86ft 18:25 / mi
shoes: Montrail Mt Masochist Mar 2011
Still feeling some after effects from the tumble I took during pickleball yesterday (soreness in the rib area under my right arm). Originally had planned a run with trailsnail but I tried a few running steps this morning and my ribs didn't like the jostling. So Homer got a nice long walk at Whiting Road instead.
Monday Jul 25, 2011 #
Pickleball 45:00 [3]
Second attempt at pickleball. Webster Park tennis courts.
My first time out, I lost both games I played. This week, I lost two and finally won my first game.
Of course, the games were all doubles, and teams were assembled more or less randomly, so winning or losing can be influenced by the partner's play as well as mine. But I think having one win and four losses does pretty much reflect my relative ability vs the rest of the people playing -- that is, worse than the average ability of the others, but not so much worse that I can't occasionally end up victorious.
Had my first pickleball injury -- I was hustling toward the net to retrieve a drop shot, and I managed to get to the ball and return it successfully; however, while doing so, I tripped over my own feet, and tumbled and rolled, landing kind of tangled up in the net. Small scrape on my right elbow and possibly a sore shoulder resulted. The particularly discouraging thing is that my shot didn't count, as you're not allowed to touch the net (as in tennis and most other court sports involving a net).
My first time out, I lost both games I played. This week, I lost two and finally won my first game.
Of course, the games were all doubles, and teams were assembled more or less randomly, so winning or losing can be influenced by the partner's play as well as mine. But I think having one win and four losses does pretty much reflect my relative ability vs the rest of the people playing -- that is, worse than the average ability of the others, but not so much worse that I can't occasionally end up victorious.
Had my first pickleball injury -- I was hustling toward the net to retrieve a drop shot, and I managed to get to the ball and return it successfully; however, while doing so, I tripped over my own feet, and tumbled and rolled, landing kind of tangled up in the net. Small scrape on my right elbow and possibly a sore shoulder resulted. The particularly discouraging thing is that my shot didn't count, as you're not allowed to touch the net (as in tennis and most other court sports involving a net).
C • net 2
Course setting 11:00 [2] 0.5 mi (21:59 / mi)
shoes: Asics Gel Nimbus 11
Checking out two map updates on the east side of Holt Rd, and one near the road leading to the tennis courts.