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

Training Log Archive: Spike

In the 7 days ending Feb 17:

activity # timemileskm+mload
  running3 2:10:00260.0
  MTB Orienteering1 1:03:54 5.87(10:53) 9.45(6:46)13c202.9
  orienteering1 52:41 4.23(12:27) 6.81(7:44)12c209.0
  Total4 4:06:35 10.1 16.2525c672.0

» now

Saturday Feb 17 #

9 AM

MTB Orienteering race 1:03:54 intensity: (11:02 @1) + (3:37 @2) + (12:21 @3) + (36:54 @4) 9.45 km (6:46 / km)
ahr:145 max:173 13c

MTBO at the Perry Bike Trails. I was psyched when Eric S decided to host this event. The map is really a work-in-progress, but it is definitely usable. I mapped the MTB trails. I've not idea how well the trail distinctions are done. I had a basic rule of:

Regular single track MTB = something I'd be completely comfortable riding
Medium MTB trail = something that I could ride, but it'd take a fair amount of concentration and would be pushing my technique a bit.
Slow MTB trail = something that'd clearly push my technique, probably enough that hopping of the bike and jogging/walking the bike would likely be faster for me.

My other rule was that I'd only map a section if it covered at least a thumb-width of trail on the final map. So a little rocky spot in an otherwise fast trail wouldn't change the trail designation, but a stretch that went say 50 meters probably would (but when I drafted the map I'd show a longer section of slow trail). It all makes sense to me, but I'd like to have a chance to see some other MTBO mapped terrain to get a feel for my mapping.

The course was fun, but I haven't been doing much biking or MTB riding. That meant my technique and condition weren't great. I was generally happy with my biking. I hopped off when I thought an area was pushing my technique too much. I crashed once when my front wheel hit some slippery mud. I walked/jogged the bike a few places where the trail had some slick mud (but only after learning how slick the mud was by crashing).

This was a lot of fun.

We ddin't get a great MTBO turnout (I'm thinking it was just 7-8 riders), but we learned something about hosting the event. Eric S seems to have worked out a good relationship with Lyle, the guy who coordinated building and maintaining the trails. That's important.

The heart rate data is weird. My HR recorded as low for the first 15 minutes. I don't think it was that low, I think the watch was wonky (it was using the optical HR).


orienteering race 52:41 intensity: (27 @2) + (48 @3) + (51:26 @4) 6.81 km (7:44 / km)
ahr:164 max:175 12c

After the MTBO, I did the regular course. My legs were shot.

The course was fun. This area is probably the nicest forest that we have in OK-land. The trail network is really dense. It makes things interesting because you constantly balance running in the woods with going off line and picking up trails. On some legs, the key is to navigate by the contours, not reading the trails on the map, but using them when you see them in the terrain.

The map is work-in-progress, but is really close to complete. There are a few old ruined barbed wire fences that need to be added or cut down. There is a bit of rocky ground that ought to be mapped.

As far as I could tell, people liked the area and found it interesting.


Thursday Feb 15 #

running 30:00 [2]

Wednesday Feb 14 #

running 40:00 [2]

Monday Feb 12 #


The 31 Day Challenge is over. I managed: 18 hours of orienteering and found
326 controls. That seems ok.

Maps I ran on: Rockhaven, West Campus, Holcom, Arboretum, Shawnee Mission Park, Pioneer Cemetery, Hard Labor Creek, Mistletoe State Park, Burcham, Landahl, Rockcrusher, Water Tower Park, RIverfront, Woodridge, Lexington Lake, Clinton Overlook, KU Edwards, Sunflower Nature Park, and Ernie Miller Park.

Noteworthy session...finding a hand gun discarded in a park (and apparently used earlier to shoot and kill someone).

The biggest challenge was that I got sick immediately after the trip to Georgia.

Sunday Feb 11 #

running 1:00:00 [2]

« Earlier | Later »