Presentation is loading. Please wait.

Presentation is loading. Please wait.

ARRL Log Checking Fact and Fiction

Similar presentations


Presentation on theme: "ARRL Log Checking Fact and Fiction"— Presentation transcript:

1 ARRL Log Checking Fact and Fiction
Dan Henderson, N1ND September 29, 2007 PNWVHFS Conference

2 A Brief History of Log Checking
Paper logs – only the top logs were thoroughly scrutinized. Because of the large number to do and the limited staff every QSO and page was not checked. 3 Penalty QSOs for each Busted

3 A Brief History of Log Checking
Early days of electronic logging still maintained the same processes. Each logging program presented the data in different formats and styles. Made advanced checking extremely difficult – and software for checking was still in its early stages

4 A Brief History of Log Checking
Cabrillo format introduced late 1999 Not a program – it is simply a standardized presentation of the log data information Not an ARRL-owned concept. Developed and maintained by an individual Now used by almost all major contest sponsors

5 A Brief History of Log Checking
Cabrillo adopted by ARRL in 1999 as the standard for its events – though not for all ARRL events (10 GHz and Field Day for example) Allowed a two-year transition period before it became the only accepted standard for ARRL events Perfect? No - It was upgraded in 2006 and continues to allow the ARRL and other contest sponsors to more easily adjudicate their contest Cabrillo works because it meets the needs of the various log checking volunteers

6 Today? Over 90% of logs for ARRL HF events and 85% of ARRL VHF events are submitted electronically This allows a more complete adjudication of scores, hence we lowered the penalty from 3:1 to 1+1 for errors Competitive paper logs are manually input into an electronic format so they can be as thoroughly scrutinized

7 Back to the History Lesson
Initial detailed cross-checking began with HF events Most participants in HF events were already submitting some type of electronic log Fewer “problem” details to resolve

8 VHF Cross-checking Initial problems with VHF/UHF events caused by several sources, such as: Reworking stations on same bands – Rovers Lax logging in many cases (such as not logging the /R for a Rover & many Rovers not sending that as part of their call – though the rules require it) Ability of a Rover to submit a second log as a Single Op Home Station Most VHF contesters were not electronically logging

9 The “missing Qs” show as NIL
Other problems Multi-Multi changing categories after the contest to Limited-Multi but deleted the non-competitive QSOs from the log The “missing Qs” show as NIL We can only adjudicate based on the information contained in the log submitted. Addressed in Cabrillo v.3 – where Limited Multis designate which 3 bands to count towards their scores

10 Another problem… Though electronic logging has made a huge difference in the work load and flow, it isn’t practical to look at each and every “problem” that may arise. When a systemic problem arises it is addressed. But again, it is not practical to handle individual situations (i.e. “Well I have a QSL card from him confirming the contact so I want the QSO and points back…”)

11 Log Checking Standards
We do not make public the individual processes or specific standards… Doing so would allow people to develop ways to “game” the system There are a couple of general principles that do guide the process…

12 Log Checking Standards
We do not bust or remove true “uniques” from a log without substantial proof… A unique is a callsign that appears in one and only one log in the database. On occasion a unique is removed – for example if it is not a valid Callsign format (FN31em – the grid was logged as a callsign) or does not appear in the FCC or equivalent database, but never without cause

13 Log Checking Standards
Callsigns and exchanged information is either “right” or “wrong” We do not use a “one-off” standard – i.e. that you missed a “dit” so what you logged as an “s” should have been an “h” so we will give you credit for it Typographical errors are penalized – Such as reversing “FN31” into “NF31” – accuracy is one of the responsibilities of the participant

14 Log Checking Standards
In a dispute we have to go with the information that is in the logs – even if N1ND sent you a QSL card for the QSO but the contact is not in the log he submitted, it’s a NIL We can not assume that since you worked him on these other bands he simply forgot to log you -

15 Log checking is not an exact science…
Each volunteer log checker has written and developed their own software for adjudicating the contest. This can on occasion cause a discrepancy The various log checkers do communicate with each other when problems arise

16 Resources website where you can input your paper log to generate and submit a Cabrillo format entry Most of the available logging programs will handle VHF contests (and several are free)

17 Questions & Contacts New ARRL Contest Manager Sean Kutzko, KX9K – starts October 8th – experienced VHF Contester VUAC Representative from Northwestern Division - Jim Aguirre, W7DHC MVP Manager – Dave Patton, NN1N CAC Chairman – Ward Silver, N0AX If push comes to shove, you can always contact


Download ppt "ARRL Log Checking Fact and Fiction"

Similar presentations


Ads by Google