Radio Society of Great Britain – Contest Committee


RSGB - Contest Committee

  • Home
  • HF pages
  • VHF pages
  • HF Calendar, Results
  • HF Log upload
  • Email alerts
  • Information
  • Privacy Policy

     
    Adjudication Principles -- HF Contests
     

    This document shows simplified definitions of the functions that have been agreed for HF contest adjudication. The information refers to contests having a serial number exchange but can also be applied is to contests with alternative or additional exchanges.

     
      1. CABRILLO LOG QSO COMPONENTS and DEFINITIONS
     

    1(a) Frequency (used to calculate Band)  Frequency in kHz on which the QSO occurred, or frequency of band edge in kHz - e.g. 3500 signifies 80m

    1(b) Mode   RTTY: RY, PSK: PS, SSB: PH, CW: CW, FT4: DG

    1(c) Date   Format is YYYY-MM-DD

    1(d) Time (UTC)   Where, for example, 2000 represents 20:00

    1(e) Sent Call   The callsign sent by the entrant

    1(f) Sent Report   The report sent by the entrant - RS(T) e.g. 599

    1(g) Sent Exchange   Exchange sent by the entrant -- if numeric with leading zeroes to three significant digits e.g. 001 represents an serial number of 1

    1(h) Received Call   The callsign received by the entrant

    1(i) Received Report   The report received by the entrant - RS(T) e.g. 599

    1(j) Received Exchange   Exchange received by the entrant -- if numeric with leading zeroes to three significant digits e.g. 001 represents an serial number of 1

     
      2. PRE-ADJUDICATION TEST OF COMPLETE LOG and ACTION
     
    2(a) Log received after submission deadline Log becomes a checklog unless mitigating circumstances are notified to and agreed with the adjudicator before the contest.

    2(b) Cabrillo structure wrong Notify entrant and request resubmission of corrected log.

    2(c) Check the Date If any QSO is outside the contest period then notify entrant and request resubmission of corrected log.

    2(d) Check the Time If QSOs are outside the contest period and appear to be incorrectly recorded, then notify entrant and request resubmission of corrected log.

    2(e) Check the Band(s), based on QSO Frequency If any QSO is on Band(s)that are not in the contest then notify entrant and request resubmission of corrected log.

    2(f) Check the Mode(s) If any QSO is using Mode(s) that are not in the contest then notify entrant and request resubmission of corrected log.

    2(g) Check the Sent Exchange If any QSO has an incompatible Sent Exchange notify entrant and request resubmission of corrected log.

    2(h) Confirm log status after pre-adjudication Logs will be either:
    a. Accepted
    b. Accepted with warnings
    c. Not accepted until corrected

     
      3. ADJUDICATION TEST OF EACH QSO LOG ENTRY and ACTION
     
    3(a) If all these conditions are met:
    (i) Received Call matches another entrant;
    (ii) Received Call there = this Sent Call;
    (iii) Band/Mode are correct;
    (iv) Time is correct +/- 15 mins;
    (v) Exchange Received matches Exchange Sent in other log (but Serial no. can be +/- 1).
    QSO is good in this log.
    For OB1s (Received Exchange when serial is "Out by One" from that shown as Sent Exchange in other entrant's log), keep a tally for each entrant for TX and flag if > 5 occurrences in contest.
    For report TX errors, keep a tally for each entrant for TX and flag if > 5 occurrences in contest.

    3(b) If the Received Call matches another entrant
    and all these conditions are met:
    (i) Received Call there is similar to this Sent Call
    (no more than two characters incorrect or missing);
    (ii) Band/Mode correct;
    (iii) Time correct +/- 15 mins;
    (iv) Exchange Received matches Exchange Sent in other log (but Serial no. can be +/- 1).
    QSO is good in this log.
    For OB1s (Received Exchange when serial is "Out by One" from that shown as Sent Exchange in other entrant's log), keep a tally for each entrant for TX and flag if > 5 occurrences in contest.
    For report TX errors, keep a tally for each entrant for TX and flag if > 5 occurrences in contest.

    3(c) If the Sent Call appears in another log without a matching Received Call in this log, and the QSO can be identified in this log, and this QSO has not already been declared good. QSO is bad in this log -- busted call identified.
    Penalty applied -- loss of this QSO plus the loss of an additional penalty as defined in the contest rules.

    3(d) If the Received Call matches that of another entrant and no matching QSO can be identified in the other log. QSO is bad in this log -- not in log.
    Penalty applied -- loss of this QSO only.

    3(e) If a matching QSO can be identified in another log but the Received Exchange is incorrect (but Serial no. can be +/- 1). QSO is bad in this log -- incorrect exchange.
    Penalty applied -- loss of this QSO plus the loss of an additional penalty as defined in the contest rules.

    3(f) If a matching QSO can be identified in another log but either Time, Band or Mode do not match. QSO is bad in this log -- incorrect logging.
    Penalty applied -- loss of this QSO only.

    3(g) If the Received Call appears in other entrants' logs and is consistent with fabricated serial numbers, or is 001 or 000. QSO is good in this log.

    3(h) If the Received Call does not appear in other entrants' logs and serial number is 001 or 000. QSO is good in this log -- unique.
    Further analysis will be carried out if the proportion of uniques in this log exceeds the average of the proportion of uniques in all logs for this contest by a configurable factor.

    3(i) If the Received Call does not appear in other entrants' logs, has serial number > 1 (or other exchange) and callsign appears in 2nd party verification. QSO is good in this log -- unique.
    Further analysis will be carried out if the proportion of uniques in this log exceeds the average of the proportion of uniques in all logs for this contest by a configurable factor.

    3(j) If the Received Call does not appear in other entrants' logs, has serial number > 1 (or other exchange) and callsign does not appear in 2nd party verification. QSO is bad in this log -- busted call unique.
    Penalty applied -- loss of this QSO only.

    3(k) If the QSO has not met any of the tests above. QSO is bad in this log -- no matching QSO found.
    Penalty applied -- loss of this QSO only.

    3(l) If the QSO is good or bad in this log and is with the same station on the same band and mode as a previous good QSO. This and subsequent QSOs with the same station on the same band and mode are marked as duplicate.
    Penalty applied -- loss of this QSO only.

    3(m) If the QSO is good and is with the same station on the same band and mode as a previous bad QSO. QSO is good in this log.
    Any additional penalty (defined in the contest rules) applied to the previous bad QSO, is removed.

           NOTES (a) Where penalties are applied in addition to the loss of a bad QSO, this will be indicated in the contest rules.
    (b) Loss of a QSO will include the loss of any new multiplier associated with the QSO.
    Updated 25th January 2022