[CQ-Contest] Not-In-Log

[DougKR2Q at aol.com]

In a message dated 8/11/99 9:14:19 AM Eastern Daylight Time, kl7y at alaska.net 
writes:

<< K*7Y screwed up, HC8A really worked KL7Y.  K*7Y sends in a log.  KL7Y
 does not.  The log checkers find the KL7Y QSO in the log of HC8A and
 cross checking erroneously shows that the QSO was with K*7Y.  The
 checking program removes the QSO, plus a penalty of 3 QSOs and takes
 away the KL7 multiplier.  >>

Sigh....this is NOT how the CQWW log checking works at all.  

If KL7Y did not send in a log, but KL7Y appeared in the HC8A log, the KL7Y 
qso would NEVER be flagged (in the HC8A log) meaning that no cross-check 
would be called for.  The only way that KL7Y might be flagged is if it were a 
UNIQUE qso (or a BAD callsign, which it is not).  But flagging alone does NOT 
result in an (as the author calls it) "automatic deduction and penalty."

As for the penalty, it is a valuable and proven tool to encourage and reward 
accuracy.  No penalty would mean that everyone could pad their log and the 
onus would be on the contest sponsor to "find the false qso's."  Sort of a 
"catch me if you" attitude.  Since Uniques are never removed for simply being 
a unique, the incentive would be there for lots of padding of logs with 
unique callsigns.  Remember, a unique is NOT removed for merely being a 
unique.

de Doug KR2Q




--
CQ-Contest on WWW:        http://www.contesting.com/_cq-contest/
Administrative requests:  cq-contest-REQUEST at contesting.com