Register | Login
Attackpoint - performance and training tools for orienteering athletes

Training Log Archive: CleverSky

In the 7 days ending Nov 11, 2017:

activity # timemileskm+m
  orienteering2 3:02:42 13.11(13:56) 21.1(8:40) 38737 /41c90%
  ignore this1 1
  Total3 3:02:43 13.11 21.1 38737 /41c90%
  [1-5]2 3:02:42

«»
1:39
0:00
» now
SuMoTuWeThFrSa

Saturday Nov 11, 2017 #

10 AM

orienteering race 1:22:54 [3] *** 9.91 km (8:22 / km) +106m 7:56 / km
spiked:18/20c shoes: Icebug Spirit

US Two-Day Champs, Beaver Dam Run, Red M35, 8.8 km, 240 m, 24th (3rd M35, 2nd eligible). Not perfectly clean, but pretty close -- it was pretty easy, virtually no route choice, just go straight. The first half or so was remarkably open woods, and I just couldn't go as fast as the terrain warranted. The errors were pretty small. Better placing than I expected.

Pretty chilly, a little above freezing, but dry. I wore my gray LS top and my RMOC O-top, and was concerned that I'd be too warm, but it was okay. My hands were cold at the start, but by #5 I had noticed that they had warmed up. Got nailed in the left hand pretty good by some greenbriar about 3/4 of he way around. I felt it, and thought, "that's gonna bleed". It was okay at first glance, but a minute or so later, I was leaking pretty good. No serious harm. I also got stopped dead in my tracks at one point when my hair got tangled in some greenbriar I was passing under, and neither was willing to let go.

240m of climb on the course specs? How did I manage to do it in 106?

splits
RouteGadget

Sunday Nov 5, 2017 #

9 AM

orienteering race 1:39:48 [3] *** 11.18 km (8:56 / km) +281m 7:56 / km
spiked:19/21c shoes: Icebug Spirit

Mt. Penn, 9.5 km, 305 m, M35, DSQ. Foggy (though I had a late start, probably worse earlier), cool, and very bad footing (rocky, and everything was wet). Pretty good run, except for two minor problems. One was that I had completely run out of brain at the end, and completely blew the last control. I started by doing a 180 and climbing instead of going downhill to the control, then after I corrected that, I made a wrong turn just before the control, and everything looked right except there was no boulder next to the trail (I was on the wrong trail), over three minutes lost. The other error was in a way more minor, but it had a more significant effect on my result. Although I went quite close to #11, I never saw it on the map, and went from #10 to #12.

Pretty unsatisfying experience with the download. After repeatedly failing to connect to the servers, I was able to do it from the Garmin website while at Nancy's house feeding her cats (she has better internet service than I do), but it didn't download this run. So I started the watch and created another dummy activity, and tried it again tonight -- it downloaded just the new one, and not this one, even though I could see the splits on the watch display. I finally resorted to copying the .FIT file from the watch while it was plugged into USB, and converted it to .GPX using GPSBabel.

splits
RouteGadget
12 PM

ignore this 1 [0]

(anchor for the comments)

« Earlier | Later »