Hi Tom,
You are right, I have never been involved in post log processing.
Change is not easy to implement and/or accept. Not long ago people said
that electronic log submission was unfair and/or would discourage
participation.
As for the examples you list, they could be handled by pointing the
participant to a web interface for log submission. I can't find it now,
but there is at least one such web interface doing more or less what I'm
suggesting. It would likely have to be augmented/modified/customized,
but doable, I think.
It may sound a crazy idea today, but who knows in the future.
Thank you for the work you do with the QSO Party.
73 de Vince, VA3VF
On 2017-04-06 9:41 PM, Tom Haavisto wrote:
From your comments, I gather you have never been involved in post
contest log processing.
Fair enough, but consider this: I look after a QSO Party, and handle
the post contest logs. This is not a complaint - I am happy to do it,
but it is interesting to see the post contest logs. Some logs don't
support my QSO Party, so folks choose "something close". Some require
repair work before I can proceed to the next step. Some folks use
old/odd software that "sorta" generates a Cabrillo spec output. I
hesitate to invalidate the efforts of a part-time entrant, lest they
decide that next year - they simply won't bother. Some must be from a
spread sheet output. The header is fine - the QSO lines are... odd, but
contain all the info I need.
I realize full well that this is MY choice - to repair the logs so they
can proceed in the log checking process, Yes - it takes time to correct
these logs, and I am happy to do it.
Consider the option you seem to advocate: "Dear contester: your log is
not in a valid format. Bzzt. You are disqualified. Please update your
logging software, and please try again next year. Signed - contest
manager". THAT would be a heartbreaking email to receive from a contest
manager... *I* would not want to be the author of one.
So - it may take an extra week or three while repair work is done -
behind the scenes, silently, without comment, but it sure beats the
alternative!
Tom - VE3CX
On Thu, Apr 6, 2017 at 9:32 AM, DXer <hfdxmonitor@gmail.com
<mailto: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
On Wed,4/5/2017 5:37 AM, Barry wrote:
>* I think logs should be submitted within 24h of the end of the contest
*>* and results should be available a month later.
*
That is unreasonable for an operation that travels to a remote location
without internet access.
73, Jim K9YC
_______________________________________________
CQ-Contest mailing list
CQ-Contest@contesting.com <mailto:CQ-Contest@contesting.com>
http://lists.contesting.com/mailman/listinfo/cq-contest
<http://lists.contesting.com/mailman/listinfo/cq-contest>
_______________________________________________
CQ-Contest mailing list
CQ-Contest@contesting.com
http://lists.contesting.com/mailman/listinfo/cq-contest
|