CQ-Contest
[Top] [All Lists]

[CQ-Contest] RDXC Log Checking

To: <cq-contest@contesting.com>
Subject: [CQ-Contest] RDXC Log Checking
From: Henryk Zwolski <zwolski@bci.krakow.pl>
Date: Wed, 11 Mar 2009 13:11:06 +0100
List-post: <cq-contest@contesting.com">mailto:cq-contest@contesting.com>
Henryk Zwolski SP9JPA

The HF QSO definition needs to be established for the purpose of 
claiming and adjudicating contest contacts.

Contest QSO Definition
A two-way amateur-radio contest contact has taken place upon mutual 
transmission and reception of callsigns and contest exchanges between 
two operators, followed by confirmation of presumed reception by both 
sending and receiving operators. Having heard (or seen in graphic 
modes) the receiving operator's confirmation of presumed reception, 
both sending operator and receiving operator may claim a "good 
contact", or a QSO each, and record their QSO's in their respective 
logbooks. Each operator shall be solely responsible for his method 
and accuracy of recording the message received (the callsign and the 
exchange).

Contest Contact Adjudication
In the event of any difference between the two QSO line records found 
in the logs submitted by the sending operator and the receiving 
operator to the contest sponsor, the contest adjudicator shall 
recognize that the portions of the message (callsign and exchange) 
transmitted by the sending operator are correct [points granted] and 
shall not grant any points only to the receiving operator for his QSO 
[BAD QSO].

The contest adjudicator shall grant points to the operator when the 
callsign of the sending operator has been miscopied by the receiving 
operator and the exchange received is correct, while the miscopied 
callsign can be associated by similarity to the sending operator's 
callsign upon comparison with the QSO data (e.g. date, time, band, 
mode). The same when the receiving operator has copied the callsign 
correctly but miscopied the exchange.

The contest adjudicator shall grant points to the operator who has 
submitted his log as a proof of sportsmanship when the callsign of 
the other operator who has failed to submit his log (the delinquent 
operator) is NOT UNIQUE, i.e. the delinquent operator's callsign is 
found at least 3 times [this threshold number can be selected at the 
contest sponsor's discretion] in the database made of all the 
log-submitting contester callsigns and non-unique callsigns.

The contest adjudicator shall not grant points to the operator when 
the delinquent operator's callsign is unique (as defined above) 
[UNIQUE], i.e. the delinquent operator's callsign cannot be 
associated with any callsign placed in the contest database.

The contest adjudicator shall not grant points to the operator when 
the operator's callsign is not found in the proper place (time frame, 
if applicable under the contest rules) in the other operator's log 
and the former operator's callsign cannot be associated with the 
callsign actually recorded by the other operator in the respective 
place [NOT IN LOG] (unmatched).

The contest sponsor shall decide how the differences in date, time, 
band, mode and RST found in the submitted log should be accounted for 
or penalized if any.

As long as there is no software for automatic log crosschecking and 
adjudication available, the contest sponsors shall ensure combined 
robot and human contest adjudication at least with respect to the 
highest score claiming operators. A contester who has sent his log as 
a proof of sportsmanship shall have the right to be adjudicated on 
his own merits, not on somebody else's errors or lack of 
sportsmanship (failing to send in his log).

For easy checking of the above adjudication options, I have made the 
following table:

Sending Operator                              Receiving Operator
Call OK Exchange OK QSO OK = 1; Call OK Exchange OK = 1
Call OK Exchange OK QSO OK = 1; Call Bad (different from sender's) 
Exchange OK = 0
Call OK Exchange OK QSO OK = 1; Call OK Exchange Bad (different from 
sender's) = 0
Call OK Exchange OK QSO OK = 1; Missing log [NOT UNIQUE] = 0
Call OK Exchange OK QSO OK = 0; Missing log [UNIQUE] = 0
Call OK Exchange OK QSO OK = 0; Not in log [NIL, unmatched] = 0

Thank you.
73, Henryk SP9JPA

Blog SP9JPA: http://sp9jpa.blogspot.com

_______________________________________________
CQ-Contest mailing list
CQ-Contest@contesting.com
http://lists.contesting.com/mailman/listinfo/cq-contest

<Prev in Thread] Current Thread [Next in Thread>
  • [CQ-Contest] RDXC Log Checking, Henryk Zwolski <=