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

Discussion: red shirt

in: CleverSky; CleverSky > 2015-11-22

Nov 23, 2015 4:27 PM # 
Based on winsplits, looks like the same guy, one Andrew Donaldson. He seems to have lost a ton of time on the butterfly loop, and then spent an hour on #20 before walking in with Sam from there.
Nov 23, 2015 4:30 PM # 
Andy is a better runner than orienteer... frequently comes to CSU events.
Nov 23, 2015 7:34 PM # 
Yep, that matches up. He was moving pretty well, able to go a bit faster than me, such that he and Tim were able to get away at the end of the first map. But he and Tim had different butterfly forks, and I saw him on the way (I thought) to our #8, looking like he might be missing it. But the splits show that he was there 25 seconds ahead of me; I'm quite surprised that I didn't see him. Then I got solidly ahead on the next leg, but his big loss came on what I thought was an easy control, although it might have been more a matter of butterfly mischief than navigation. Meanwhile, I had no idea that I had gotten ahead of Tim in the butterfly, to the tune of four minutes. I had thought that I caught him at #15, but he was actually catching back up to me.
Nov 23, 2015 8:17 PM # 
what I thought was an easy control

I guess they are all easy if you go right to them, but I thought that one (your #8, my #11) was relatively difficult, obscured by green from below and on a pretty dinky rock. I thought that might be one that some of the less experienced folks would find quite difficult.
Nov 23, 2015 8:59 PM # 
Ah, ok, misunderstanding on my part, and now things make more sense. Winsplits apparently has the splits permuted to the B ordering, but when I look at it in Attackpoint I can see that it was #8, not #11, where he had trouble. I headed up the small trail toward #8 and saw him crossing in front of me heading to my right at high speed on the larger trail. I attacked from the trail junction, but he was at that point making good time toward oblivion. That explains why I didn't see him at the control, he didn't get there 25 seconds before me, he arrived 24 minutes later. It was a tricky control, though my guess is that it was a long time before he started wandering around in the right area looking for it. Unlike your #8, my #11, which I did think was easy.
Nov 23, 2015 10:14 PM # 
Agreed. That one (my #8) was pretty trivial. AP shows me losing time on my #11, perhaps because I was walking anyway, and also because I slowed down as I was getting close, both because it was pretty thick from below (where I was) and because Ken and another guy were thrashing around well off to my right and I was wondering just a little what they were up to, even though I was mostly confident I was doing the right thing. Still, I went more or less directly to it, so I thought of it as a spike.
Nov 23, 2015 11:07 PM # 
Same one I had trouble on, I think I cut uphill a little early and misread contours in the thick before moving to my R and coming around to the tiny boulder...

AP also shows me havinf an error on #2, but that is because I went more direct cross country and the trail option wide was undoubtedly quicker. But I executed my route just fine so don't really call it an error...
Nov 23, 2015 11:31 PM # 
AP and winsplits have different error algorithms. Winsplits totally missed my 2 min error on 5, although pretty hard to see perhaps in a leg that took me 27 min.

This discussion thread is closed.