Register | Login
Attackpoint AR - performance and training tools for adventure athletes

Training Log Archive: Gswede

In the 7 days ending Nov 11, 2017:

activity # timemileskm+mload
  Orienteering4 3:47:52 22.93(9:56) 36.9(6:11) 74094c124.7
  Running6 3:35:00 24.23(8:52) 39.0(5:31) 40043.0
  Core O'Clock1 25:005.0
  Total8 7:47:52 47.16 75.9 114094c172.7

«»
1:53
0:00
» now
SuMoTuWeThFrSa

Saturday Nov 11, 2017 #

Running warm up/down 20:00 [2] 3.0 km (6:40 / km)

10 AM

Orienteering 1:09:06 [4] *** 10.98 km (6:18 / km) +230m 5:42 / km
24c



A few issues in this course. I was rushing far too much at the beginning. Somehow my watch stopped immediately after the start and I had to start it again at 7.

The main incident that took me out of this course was at #16. I allowed the green to push me to the right and onto the eastern spur. I relocated at the boulder and artificial X and took a bearing into the control from there. But when I made it to the two knolls, the control wasn't there. I assumed I had swung too far right and decided to backtrack: nothing. Then I followed the spur north and eventually found it, although it seemed a little off.



After checking with my GPS track and the tracks of four other blue runners, it looks like 16 was misplaced. I think this contributed to my mistake on 17 afterwards also as I was out of contact with the map from the start.



It seems that if you attacked it from the south, there was no problem. Perhaps most people assumed they were running slower than normal because of the green. But my attack from the east lost me time there. Looking at the two-day totals, it looks like I lost the championship there.

I certainly don't mean to badmouth the organizers. I thought the terrain and courses were excellent. They did a great job putting on a fun weekend. But it's still frustrating to lose a championship on a control like this.

It also didn't seem like a good idea to lodge a complaint since who wants to throw out a championship race, particularly when it's in its final year.

So, there it is; a misplaced control and a lost race. It's not the first and likely won't be the last. Take it in and move on to what's next.

Once again, I want to express my gratitude to QOC for the weekend. There are so many things that can go wrong in orienteering. They did a great job making everything run smoothly.

Friday Nov 10, 2017 #

Running 35:00 [2] 7.0 km (5:00 / km)

Easy morning in Rock Creek with Boris and Luis. Beautiful area.

Thursday Nov 9, 2017 #

Orienteering 45:00 [3] *** 6.0 km (7:30 / km)
15c

Getting out onto the Prince William model map. Super fun woods. Excited for this weekend.

Wednesday Nov 8, 2017 #

10 AM

Orienteering 29:52 intensity: (6:52 @2) + (11:00 @4) + (12:00 @5) ** 5.69 km (5:15 / km) +134m 4:42 / km
29c



Finally had a chance to rerun the sprints I helped set this summer for DVOA's sprint series. This one was at 80% and had a two minute rest.



Second sprint. This one done at 90% with no break. There was a deer at #5, took about 15 seconds to scare it off before punching the control.

Running 30:00 [2] 5.0 km (6:00 / km)

Tuesday Nov 7, 2017 #

Running 45:00 [2] 9.0 km (5:00 / km) +200m 4:30 / km

Another easy day in the WIss, but this time with Luis. Left foot is much better, but still slightly bruised.

Core O'Clock 25:00 [2]

100 pushups, 20xpedestal, 5 minute calf raise, 10 minute plank

Monday Nov 6, 2017 #

Running 55:00 [2] 11.0 km (5:00 / km) +200m 4:35 / km

Showing Viol the Wissahickon, Tedyuscong, Covered Bridge, Great Beech.

Weighed myself this morning at 156 lbs (70.7 kg) Just a bit above racing weight. Perfect timing for the Classic Champs.

Sunday Nov 5, 2017 #

9 AM

Orienteering 1:23:54 [4] *** 14.23 km (5:54 / km) +376m 5:13 / km
26c



A pretty great course on Mt. Penn. Really fun design by Erik Eddy.

The mistakes I made were slight bobbles going into controls (4, 11, 23) but overall I felt pretty good. It was quite clear that the change from very low visibility in Hickory Run to the excellent visibility on Mt. Penn was a big change.

Pretty happy with my routes, but I could have executed 11->12 better.

Running 30:00 [2] 4.0 km (7:30 / km)

« Earlier | Later »