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

Discussion: Harris

in: CleverSky; CleverSky > 2020-05-02

May 3, 2020 9:46 PM # 
Insanely hard place, but really fun. Unfortunately much too far for me to contemplate driving there these days.
May 3, 2020 10:05 PM # 
It might also start getting annoyingly buggy very soon. That's what really wrecks that place. It's nicer in the fall.
May 4, 2020 8:17 PM # 
Looking up Ernst's entry, it looks from his route that his watch stooped two or three times while he kept moving (hit the wrong button, I assume). And maybe you time was better by a good bit?
May 4, 2020 9:28 PM # 
My guess is that he lost GPS signal, but the watch was still keeping time. If he had taken splits, it would be easier to figure out.
May 4, 2020 9:41 PM # 
But the little red dots, if you hover the cursor over them, show the amount of time the watch was stopped. You know that, right?
May 5, 2020 12:36 AM # 
Oh, right, that's what those are. But then the overall time is still correct, isn't it? Do the red dot times count in the total?
May 5, 2020 12:43 AM # 
Hmm, no, it looks like they don't. And in fact, it looks like for the first couple of those, what was probably happening was as you say, that he was hitting the start/stop button on the watch at controls, rather than the splits button. It stops at 1, resumes at 2, stops at 3, resumes at 4...
May 5, 2020 12:44 AM # 
Yes, in this case. See how there is a straight line line adjacent to each red dot. That's a sign that Ernst was moving but the watch was stopped. So when the watch started again, the GPS has him in a different place, hence the straight line connecting. But to get his time you have to add the stoppage time.

Whereas, when Phil is on a run and stops his watch, he also stops (for a heart issue, or to poop, or to stretch, or to rest). He's not moving. So you can make a (weak) case that the time his watch shows at the end is a valid time. No so in Ernst's case.
May 5, 2020 2:50 PM # 
The red dots are very useful for knowing how your time really compares with others. On some of the winter training courses, people put up bogus splits. In one case I remember, if you look at the track the person stopped at virtually every control for a minute or two! I took the winter courses seriously enough that if I put up splits, they were legit.

It's tempting to go to Harris this weekend just because the two times I know of, by people who normally are quite a bit faster than me, are very soft!
May 5, 2020 6:32 PM # 
Well, sort of legit. How much time was spent studying the course in advance?
May 5, 2020 6:50 PM # 
Is legit ever in the eye of the beholder!
May 5, 2020 7:53 PM # 
With this much trash talk, I'm really looking forward to Phil's excellent performance.
May 5, 2020 8:10 PM # 
Now it's three times I know about, all over 20 min/k. The pressure will be on to only make 15 minutes of mistakes. I'll definitely need to "study the course" for a couple of hours before I head out. And my back has to cooperate.
May 5, 2020 8:41 PM # 
My per km times on my previous visits to Harris Center were 16.5, 21.4, 17.2, 18.6, and 20.5. The best by anyone on any course that I've run has been 12.2, by Ethan Childs.
May 5, 2020 9:19 PM # 
I added my splits here.
May 5, 2020 10:58 PM # 
My per k times were 16.6 (green), 17.3 (green), 18.7 (red) for the courses in 2015, 2016, and 2017. They were over 20 last year for the two UNO o-ringen courses when we had already done three courses in warm weather, and I was too beat to run at all.
May 5, 2020 11:18 PM # 
A couple of those times of mine were at meets that Alar put on for Father's Day, and it was oppressively hot (and buggy). Of course, it's getting that way now, too.

Looking at the rate that you were slowing down between 2015 and 2017 and applying a best fit, we can extrapolate to 2019 and get a consistent result to what you said, and to 2020 and come up with the prediction that you will take 1:55 for a 5 km course.
May 5, 2020 11:58 PM # 
Yep, 2016 and 2017 were Father's Day, hot and buggy. Sad to say, your projection may prove prescient. Time will tell.
May 6, 2020 2:53 AM # 
PG, thanks for setting up the AP event for this.

The best I'm aware of so far on this course is jima: 1:25:52 (17:10/km).

Of course it's long and difficult. All courses set by LR are long, all courses at Harris are difficult.

I've been meaning to get out there before the bugs. Oh well. Now I'm intending to get out there before the leaves. I think that gives me a couple of days. There's also the matter of getting out there before dark, but that's a personal problem.

My pace for the two days of the 2015 Boulder Dash was 11:44/km and 16:13/km. That's for brown, behind bl the first day and kadley the second. Can't lay my hands on the local meet results since then, but I'm pretty sure I was quite slow.
May 6, 2020 5:54 PM # 
Yes, my watch stopped a few times - it happens frequently in O-ing - losing signal or hitting the watch against a protruding object - and possibly I may have pushed the stop button instinctively when I stopped for something - it has become a habit. I lost 27 minutes on 8 bumbling around trying to figure out the map, not worrying about time, just wanted to be right - but was utterly wrong! The watch stopping happened at the beginning, maybe 6 minutes? I need to relearn how to do splits - totally spoiled by e-punching!!

Please login to add a message.