[NLRS] Logging Accuracy During Contesting

[Clare Jarvis]

Hi Club members,

If you do log using   W0ZQ/EN43 because your software works that way, you can 
use an editor such as notepad to globally replace W0ZQ/EN43 with W0ZQ/R.

That maybe easier than putting up with false dupes in your software.

73   Clare  de K0NY



On Friday 19 January 2007 11:03 am, w0zq at aol.com wrote:
> Hello NLRS land.
>
> It appears that the League is now running our VHF contest logs through
> their error checking process. Overall, this is good news. Many of you
> may have seen your Log Checking Results (LCR) from the June contest. I
> believe (but do not know) that our September LCRs may be available
> soon.
>
> I can tell you that their are some "strange" LCR results ..... I say
> "strange" because I'm not saying that the LCRs are wrong,but "strange"
>  from the standpoint that we don't understand how we got from our
> original (submitted) score to what eventually gets posted .... in some
> way that information is contained in the LCR. So while we wait, and
> while we continue to work to understand LCRs, I do have the following
> HIGHLY recommended suggestions for this weekends contest.
>
> 1. Make sure your logging is accurate. WOZQ is not W0ZQ ("oh" vs zero).
> That will get you an error. With all the VHF/UHF & microwave bands,
> make sure that you log the right band. Time should be close. Mode does
> not matter. Make sure your enter the grid data correctly.
> 2. Make sure that you enter a contact WHEN you make it, not later. For
> example, if I run N0KP up through the bands and forget to log the 5.7
> GHz contact, Dave will have that (good) contact removed from his log
> along with a penalty QSO ... that's two QSOs that I cost Dave for MY
> logging error. So, make sure you log all contacts as you make them ....
> don't wait.
> 3. IMPORTANT. It appears (but can not confirm) that the only "legal"
> rover call is those followed by a /R, like W0ZQ/R. W0ZQ/EN35 is not a
> rover call and it will generate an error. Some logging software
> programs will treat W0ZQ/R in EN34 as a dupe with W0ZQ/R in EN35 so
> many of us use W0ZQ/EN34 and W0ZQ/EN35 to distinguish between these two
> rover QSOs. For us, its obvious its a rover. I suspect that the Leagues
> log checking software will kick these out as invalid contacts with a
> possible penalty involved (speculation on my part). I recommend that
> all rover calls be indicated with just the /R and that you find another
> solution to the log duplicate issue. Please be aware that your logging
> software score itself is NOT used by the League whatsoever, so its OK
> if it shows up as a "dupe" in YOUR log checking software (ex: W0ZQ/R in
> EN34 and W0ZQ/R in EN35) as it will not in the Leagues LCR.
> 4. If you log a rover without the /R, it may also be an error. W0ZQ is
> not W0ZQ/R. If you work a rover, make sure the /R and only the /R goes
> on the end of the call.
>
> 73, Jon
> W0ZQ
> ________________________________________________________________________
> Check out the new AOL.  Most comprehensive set of free safety and
> security tools, free access to millions of high-quality videos from
> across the web, free AOL Mail and more.
>
> _______________________________________________
> NLRS mailing list
> NLRS at mailman.qth.net
> http://mailman.qth.net/mailman/listinfo/nlrs

-- 
Mr. Clare Jarvis
Jarvis Computer Software
PO Box 1264
Winona MN 55987-7264

(507) 454 2575

Reply to: jarvis at jarviscomputer.com