Dear fellow contesters and especially contest authors
I am currently developing a new computer program to check the logs for the
UBA DX contests to be used from 2010.
The project is in an early stage but I am testing with the logs of the 2009
logs for both modes and although the UBA adopted Cabrillo, there is a wide
variety of exotic interpretation to this format. Writing routines to catch
all possible exceptions to the standard has been a pain so far. The weirdest
things pop up. Some logs are even mutilated beyond recognition by the
submitter, like:
QSO: 3500 CW 2009-02-28 2227 CA0LL 599 117 -- DUPLICATE
Or
QSO: 3500 PH 20 - - CA0LL 000 --
000 --
CA0LL is a bogus call of course. And there are many other mangled cabrillo
logs in my 'busted logs' folder.
Most familiar contest calls have it right because they use the right
software. But PLEASE dear contesters, DO NOT remove dupes from the log or
mangle QSO information. Do not edit logs unless you know what you're doing -
which means making sure that the log still complies with the standard.
The Cabrillo format as specified by the UBA can be found here:
http://www.on7ss.be/pdf/uba_contest_cabrillo_template.txt
Software that currently 100% adheres to this standard:
N1MMLogger, WinOnContest by ON4AVJ, SDU by EI5DI.
Win-Test does NOT put the province in the log when the PARTICIPANT is
Belgian.
The other software (another 40 different brands!) that is commonly used does
not produce the right format. This is not always because it is a bad
program. Sometimes operators use software that is either not up for the job,
or has been ill configured.
Software authors: if you support the UBA DX contest, please check if your
code follows the standard.
Participants: please check if your software actually supports the UBA DX
contest.
Please spread the word.
73 de Franki ON5ZO
_______________________________________________
CQ-Contest mailing list
CQ-Contest@contesting.com
http://lists.contesting.com/mailman/listinfo/cq-contest
|