Mis-punch issue with Start/Finish

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Mis-punch issue with Start/Finish

Bcard74
Hi everyone.

Love the app and am just starting out setting up some of my own courses. Yesterday I tested one out and had a mispunch error seemingly because of the start position. It looks like because I had to run back across S1 to reach the finish it created a problem and I could not resolve it.

I have redone the course and dropped S1/F1 on top of each other - is this the preferred method for a course that starts and finished at the same place? Will that alleviate my issue? Everything else worked perfectly but since it is pouring rain here in Canada today I am hesitant to head out to try again.

Any tips or tricks are sincerely appreciated, I have included some screenshots that may help explain the issue better than I.

Sincerest thanks in advance for any help you can provide.

Reply | Threaded
Open this post in threaded view
|

Re: Mis-punch issue with Start/Finish

MichaelRaz
This post was updated on .
Bit hard to tell from the screenshot but my guess is that the S1 is not the issue.  The Results screen shows all controls that are punched even if duplicated or out of order.  Just like a standard SI based course, the software just ignores extra punches but then still needs to have the complete and correct course punched within the list.  Likely this is an actual mispunch but cannot tell from the partial screenshot. Look for controls that you missed or punched out of order.

After you hit the start control, the finish will not punch until you have punched at least one control. If suitable (and often the case), the two can be co-located but this is not required (strongly encouraged for Start Anywhere courses) - the challenge is in planning the course so the chance of running close to the finish on your way to another control is very unlikely (but runners need to be aware of this anyway).  Maprun7 (along with the new console) allows for more flexibility with this as a finish punch can be confirmed either manually or by stopping for a period of time so it seems as if you did want to punch the finish.  Continue running and punching another control will cause the initial finish punch to be ignored. See https://maprunners.weebly.com/maprun-version-7.htm 

Not sure where in Canada you are but, yes, it's going to be a wet few days!

Edit - looking at the screenshot it even looks like you did not hit 42 (although your track may be just off the edge??  I assume this was a point to point course?
Reply | Threaded
Open this post in threaded view
|

Re: Mis-punch issue with Start/Finish

Bcard74
Thanks for the information.

I re-ran the course and it seemed to work ok except it wouldn't score. I just saw that using Open Orienteering Map will not score, guess that is my issue.

Appreciate you taking the time to help out! I am near Burlington in Southern Ontario...
Reply | Threaded
Open this post in threaded view
|

Re: Mis-punch issue with Start/Finish

MichaelRaz
I was wondering about the type of course (hence my question about point to point).  When you say "wont score" is this a score-O you are trying to set up because a score-o should not have a mis-punch. Feel free to post any more information/question. With maprun6 and the corresponding console, the type of course (and scoring if a score-o/scatter) needs to be in the course name (KML). This is transferred and locked in the options setup.  With Maprun(7) and the new console, the setup can be down in the options only.  Lots of good information on the website.

I'm in Ottawa and about to head out for a wet and chilly event with our club. I handle the Maprun (and routegadget) for OOC - not an expert but happy to help when I can so feel free to post or send me an email with questions.
Reply | Threaded
Open this post in threaded view
|

Re: Mis-punch issue with Start/Finish

Bcard74
Thanks - perhaps I can send you a message so not to clog up the forum with inane questions.

Have a good run!