Error free is one thing but, in consistent Cabrillo format is something else!
There are at least 7 different formats of Cabrillo I see just for the Makrothen
RTTY contest alone – they are all conformant to the Cabrillo spec but most do
not conform to the Cabrillo template provided for the contest by it’s sponsor.
For example, some QSO records include a signal report despite one not being
required in the Makrothen exchange; some include additional fields at the end
of the record indicative of either which radio made the contact or which
station as part of a multi operation.
Particularly in RTTY, there are a small number of errors in a log resulting
from “clicked on the wrong place” QLF’s – this can have an exchange that is
599CM87 instead of CM87 in the log record. Some miss the exchange and insert
XXXX or have an invalid grid locator.
For the most part, processing these errs on the side of benevolence. If
something is obviously and unintentionally broken, give the benefit of the
doubt and fix it – for example the 599CM87 gets manually “fixed” to CM87 – if
that’s the wrong exchange, well then it’s too bad and the log checking process
deals with it accordingly.
So, the process is:
- Collect
- Normalize
- Log check
- Generate results
- Proof results
- Publish
PL259’s goal for the Makrothen contest is a month post the log submission close.
Stu K6TU
On 4/6/17, 6:32 AM, "CQ-Contest on behalf of DXer"
<cq-contest-bounces@contesting.com on behalf of hfdxmonitor@gmail.com> wrote:
I agree, it's unreasonable to expect log submission within 24 hours,
not only for the reason mentioned, but also to give participants some
breathing time after the contest. This way they can review the log,
and deal with any issue that would cause the CC to spend time
correcting errors on participants behalf.
That said, I think the CC should not get involved with correcting any
submission errors. I see it as part of the participants responsibility
to submit a log that is error free. In this case, final results after
a month or two may be possible.
Nothing above is to compromise compliance with the contest rules, such
as any form of cheating attempt. I'm talking strictly about the time
the CC spends fixing 'benign' issues.
73 de Vince, VA3VF
_______________________________________________
CQ-Contest mailing list
CQ-Contest@contesting.com
http://lists.contesting.com/mailman/listinfo/cq-contest
_______________________________________________
CQ-Contest mailing list
CQ-Contest@contesting.com
http://lists.contesting.com/mailman/listinfo/cq-contest
|