Register | Login: pw: 

Attackpoint - performance and training tools for orienteering athletes

Training Archive: PBricker

In the 7 days ending 2006-04-08:

activity # timemileskmclimb
  Orienteering5 2:34:33 9.29(16:37) 14.95(10:20) 125
  Trail Run3 1:35:29 11.1(8:36) 17.86(5:20)
  grass1 38:18 4.9(7:48) 7.89(4:51)
  Trail/Road Run1 24:00 2.5(9:36) 4.02(5:57)
  machines1 22:00
  Total11 5:34:20 27.79 44.73 125
[csv]

«»
1:26
0:00
» now
SMTWHFS

Saturday Apr 8

Event: NEOC Spring Rock Festival and Intercollegiates
 
Orienteering 53:05 [4]4.7 km (11:18 / km) +125m 9:58 / km
NEOC A-meet, day 1, red course (M45), at Wells State Park. Didn't feel comfortable or confident out there, and made some stupid mistakes (totally about 4:00). (Well, I guess almost all orienteering mistakes are stupid, but some are stupider than others.) I didn't much like the terrain, and I often felt unsure exactIy where I was on the map. I guess I'm still trying to move a tad faster than my skills can handle. But a "bad" day now isn't nearly as bad as it used to be a couple years ago.
Orienteering 20:52 [5]2.1 km (9:56 / km)
Ran the second leg of three person team with Jeff Schapiro running first, Jeff Saeger running last. I had the "long" course. My legs were dead! especially for climbing hills. Then I choked the penultimate control and maybe lost 45 seconds. That, plus a very bad route choice, made this a mediocre result. We were a three-point team, so not really competive no matter how well I had done.
Orienteering 13:00 [3]1.5 mi (8:39 / mi)
Warm-ups before each race.

Red Day 1 - Splits

Sprint C - Splits

Thursday Apr 6

grass 38:18 [3]4.9 mi (7:48 / mi)
UMass loop clockwise, running almost entirely on grass or dirt alongside the road. Had a bad case of runs during the run, requiring an emergency pit stop in the math building. Caught a virus over the internet from Peter?
C • Nope, if you'd caught mine you... 2

Wednesday Apr 5

Trail Run 55:19 [2]6.0 mi (9:13 / mi)
Slow running on trails at Mt Norwottuck, south side. Practiced mapreading on the move. Legs tired and stiff.

Tuesday Apr 4

Trail Run race 21:10 [5]3.1 mi (6:50 / mi) vdot: 46.5
The first Tuesday night cross country race of the season. Temperature was a wintery 35 with flurries, but I didn't mind. I placed 5th, about 30 seconds behind Rich Clark; I guess all the fast runners are afraid of the cold. My predicted time was 21:30, so I was pleasantly surprised to be a bit faster. Legs felt good, but I need to work on conditioning and speed. Goal is to get under 20 minutes this season, but I would need to stay healthy for an extended period. What are the odds of that? 6:37, 6:41, 7:09, 41.
Trail/Road Run 24:00 [2]2.5 mi (9:36 / mi)
Slow running before and after. There was a bear hanging out around the abandoned buildings of the old state hospital, about 100 meters up the hill from the Smith fields. We stared at one another about 30 feet apart until he got bored, and wandered off. Reminded me of my bear-of-a-dog Kayla.

Monday Apr 3

machines 22:00 [3]
Elliptical. A new machine, "Octane", with lots of bells and whistles including a button that says "glute kicker". I abstained.

Sunday Apr 2

Trail Run 19:00 [2]2.0 mi (9:29 / mi)
Slow warm-up for the two sprints. It seemed clear I wasn't going to have a lot of zip in the legs, but that was a minor problem ...
Orienteering 38:10 [4]3.08 km (12:24 / km)
First of two sprints at Needham, first time on the map. When I turned over the pre-printed map, I couldn't see the control circles or the numbers or the connecting lines very well: the pink and the brown contour lines just all mixed together; and the course crossed itself 14 times. That contributed to two bad errors: I skipped 4 and went straight to 5; when I noticed I hadn't yet punched 4, I went back for it, then back to 5, adding about 570 meters and about 6 minutes. Then, leaving 7, I ended up on the southern trail that came in south of the control when I thought I was on the northern trail that came in north of the control. (Was I looking at the circle for 10 when I exited from 7? In any case, I obviously wasn't looking at the map much while running on the trail). Then I checked out a control in the parallel location before figuring out where I was, losing 3 minutes. (Scott Turner apparently did exactly the same.) 9 minutes is a lot of time to lose in a 3k sprint!
Orienteering 29:26 [4]2.66 km (11:04 / km)
sprint 2, time for redemption -- not. I was being very careful to follow the lines between the circles, obsessively checking that I was going to the right control (this course only crossed itself 6 times); but I bungled three (yellow level) controls, losing about two and half minutes total. Of course, the problem was the familiar one for me in sprints: too much running, not enough map and terrain reading. Just didn't feel prepared (yet!) to be orienteering at this pace. Lead to some poor route choices, and not enough looking ahead (which is especially important in the sprints).

Sprint 1 - Splits

Sprint 2 - Splits


 

Aug 21, 2008: processing time: 0.134s | © 2000-2008 Attackpoint
contact | about orienteering | donate