okansas.blogspot.com Occassional thoughts about orienteering |
Saturday, April 19, 2003 A few comments on post O' race analysisNow and then I get an email with a suggested topic for this page. A couple of days ago, I got a mail that included:..how do people perform their post race analysis and record their results for future use? ...when I was only running, a simple log of workouts was easy. I'm having trouble compiling and storing all this O data in an efficient way. Here are a few thoughts about the topic: I'd guess the most important (and useful) thing to do is draw your route on the map after a race. Keep the maps and look at them now and then. It doesn't really matter how you file the maps. Mary keeps her maps organized by location (state). That's quite nice. When we are traveling, I can go into Mary's files and find the maps. I used to keep my races in notebooks by date of race. It was interesting to go over an entire season and see how I'd improved. These days I keep my race maps scattered around the house (eventually ending up in a big plastic box). Attackpoint is a slick tool for recording training and racing. The more people who use it, the more interesting it gets. More and more people are also scanning their maps so others can take a look at how they ran. Sergei Zhyk and Peter Gagarin have a lot of maps on the web. Some people draw little arrows on the maps to indicate the features they used to navigate (e.g. the attackpoints). That seems like a good idea. It would be an interesting exercise to sit down after a race with a blank piece of paper and draw a sketch map of the race. The sketch map would show the features you remember using to navigate. I used to spent a lot of time writing about my races. I'd write about my plan for the race, how I ran each leg, what I thought of the map and terrain, how my running felt, and so on. I had a rule -- no matter how simple the leg, I had to write at least one sentence. Writing forced me to spend a bunch of time thinking about the race. That is almost certainly a good thing. I've found it important to spend a lot of time thinking about what went well rather than what didn't go well. Most of us focus on booms and bad route choices. At the end of the race, everyone is talking about what they missed. For me it is more important to try to understand what happened when I didn't miss. If I spiked a control, how did I do it? If I was running fast (which doesn't happen any more!), why was I able to run fast? posted by Michael | 3:05 PM
Comments:
Post a Comment
|
|
||||