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

Race Evaluation

Moscow Meridian 22: Score

Tundra/Desert

1. Bad route choice
+00:50
(42) The route is here. I picked the direction from the start that jumped at me. I could see that there were controls on the peninsula but also couldn't quite see the peninsula from the start, only the water that lay between, so decided to figure out how to get to it later. The error I put here is the difference between the ideal (Superman's) time for the ideal route that the computer figures out after the event, and Superman's time for my route, scaled to my speed without the other three mistakes and with the ControlĀ 33 error accounted-for separately... hopefully this is understandable. In other words, the time loss for this leg is my best guess of what I lost just from choosing the wrong order for the three obvious loops.
2. (45)
3. (44) I was mostly alone by this point, maybe one person ahead. I passed this person at the control.
4. (43)
5. (41) Some dude who I punched ControlĀ 43 with decided to follow the river (low route). I could see his headlight trailing hopelessly.
6. (37) Looks from the splits that the safe left route that I took was not much slower if at all.
7. (38) I could see people leaving the control via the approach trail, so found it without problems.
8. Did not read control description
+00:35
(39) I couldn't find the control right away, so stopped to look at the descriptions, then found the feature and the control behind it.
9. Bad compass work
+00:25
(40) Went too far left (wanted to, but not that far), then was slow looking for the control. The fringe of the forest was flooded and the mapped trail was underwater, so it was hard to understand where to look for the bag.
10. (36) I think I used the trail that I showed on the drawing, but I'm not sure; whichever trail it was, was made wider by some equipment. I got down to the trees and couldn't figure out much. People were running past but I didn't understand what was forest and what wasn't. Then I heard the SI unit beeping just to my right. Don't think there was a time loss here, it must have been confusing for everyone who didn't take the lagoonside trail, which was slower.
11. Did not plan ahead
+00:25
(32) I should have followed the edge of the lagoon. Instead I followed a trail through the dead nettles out of ControlĀ 36. Not sure where I got to the main trail; this is the one place on any given course where I try to draw the route and there is a total blackout.
12. (33) I confused the indistinct side trails just before the control. Not a time loss.
13. (34) Not sure where I was in the fire rings, but hit the trail too far right and figured it out almost immediately.
14. (35)
15. (46) Tried to push on this leg, and following this one.
16. (48)
17. (47)
18. (49)
19. Bad route choice
+00:35
(31) I kept thinking that 33 probably belonged on this leg but it was too late. I put this down as a second control-sequence error, estimating time lost from the splits.
F. (F)

Total Time Lost - 00:02:50


Split Analysis

back to race