I hate it when people are still out late, hope those last two came back while it was still a great sunny day.
Everyone came back on time at our MTBO event yesterday but unlike sunny NSW, WA got flooded.
Yep, its always sunny here.
It rained when I did MTBO there back in March. Actually it's rained at all three MTBO weekends I've ridden at so far this year. I should hire out our sport to farmers.
OK, I see results now and I can see that at least one of the missing runners won W40A in just over 4 hours. That is a brilliant effort for someone running maybe their third hard course.
I'll try and achieve that same feat of winning M21E in just over four hours this weekend.
The middle distance that is, not the long.
Just over 4 hours is some commitment to finishing the course, and she wasn't the slowest....
I thought NSW events (used to) have a 3hr time limit after which competitors become disqualified?
Another glorious orienteering rule. Was that in the absence of course closure times or something?
I think Elites have a strict 3hr limit. Typically it's course closure, which at least for a WA standard event gives you 3.5hrs (or 4hrs if you wrangle your way into a 9am start).
Routegadget by course
control 14 (#114) removed from AP splits for Hard 1 - bad timing. There may be some other dodgy control units, but none report as negative splits
Thanks - did they send you the splits by course as XML 3 ?
(I put that into the OZ fork of MEOS for someone on AP, but have never tried it in anger)
I request splits in csv format, XML2 by course, and XML2 by class. The csv file was just the results, so I worked with the "by course" file, and didn't worry about "by class"
For AP splits I deleted the 13-14 leg on Hard 1 because #114 (control 14) was giving dodgy times and negative splits sometimes - I had already loaded RG so just guessed some times and adjusted the seconds for the leg in the kilpailijat_nnn.txt file, based on Lachlan's gps track.
Thanks - I need to make the by course stuff visible again in the next version, sounds like its good enough.
Are your SI bricks synched as meticulously as ours are (i.e. whenever someone diligent sets a course, about every ten events)?
We sync start/finish for every event and the others if the previous event was over a week ago. I can't speak for other clubs. I think most (or at least some) results software lets you adjust times read from a control.
One of the units in the field was programmed as a check unit on Saturday - one small step from an interesting accident.
I think good practice is for the planner to punch every control in sequence when they collect them and then print their splits (the SI Printer lends itself to this). That way wrong times, codes and functionality can be detected before an accident [Shingo makes me do this].
We never change the code of SI boxes, so dont need to worry about this
Either do we but we frequently have sync issues from people not doing it, which are quite noticeable at sprint events (or when doing the dishes).
We synch on a regular basis, and always before a major
I don't know anyone military of that rank, could be difficult to do here.
Major
Majors are field rank officers who command a sub-unit – a company, squadron or battery
Not surprising though. You could put the major in charge of the SI unit's battery. They always seem to be playing up so need some kind of officer in charge. I guess Jim was around in the war days so knows of such things.
Careful tRicky - you are coming east shortly and Jim may have a welcoming party for you. Sorry about Canberra weather this weekend.
You mean the fact that it's forecast to be -1 degree overnight? I packed a jumper :-D
Where did Rockman go?
I found my mittens and arm warmers in the car too so I'll chuck those in, not that I feel the cold or anything.
I think the weather in Canberra is lovely at the moment, nice and fresh
Yeah I didn't need the mittens or arm warmers.
This discussion thread is closed.