Committee notes 2000

  << back

Results 2000 notes

Log – checking software: Zdeněk Šebek, OK1DSZ
Contest Director: Martin Huml, OK1FUA / OL5Y
Error logs for all electronic submissions: ask to okomdxc@radioamater.cz
“RC” abbreviation: R - see "Station descriptions", C - see "Comments"
“Log” or “L” abbreviation: E - e-mail or disk, H - handwriten, !!! - printed, not provided data
Learn how to create Cabrillo logs. Even “standard” programs such as TRLog or CT can produce their native data files with different content depending on their configuration.
- If you use one of the well known contest log programs such as TRLog, CT or SuperDuper and submit their native data files, do not try to edit these files. All data files are imported into database by utilities dedicated to all these logging programs. If you corrupt expected format of data files, import procedure would probably fail and all your changes will have to be removed.
- If you really need to edit your log or if you are rewriting your paper log into computer, please, use only editors working with plain text files. If you use programs like MS Word, do not forget to save your file as a plain text, never use MS Word’s native format DOC. The worst case is if you put all your QSOs into a table in an MS Word document. If you do not have any other choice than using MS Office, then a MS Excel table is.
- A lot of stations entering SOAB and several SOSB categories have submitted separate logs for each band. Better way is to submit one big log covering all bands and several summary sheets.
- Check your logging software carefully. Some of you have lost points because of error in call-sign where this call-sign was longer than 8 characters. For example PT2/KC2BA instead of PT2/KC2BAA. I am afraid that their SW cut longer call-sign to 8 characters.
- Check time on your PC and offset between your local time and UTC in your logging software setup.
Frequent errors
- Error in the call-sign. Pay attention to your VOX delay. If it is too long, you will not be able to hear the first dot of caller’s call-sign, or the first dash will be shorten to dot. So, you will log UA9 instead of KA9 etc. If you are on non-OK/OM side of this particular contest, it is probably not so important, but the CQ WW is only two weeks later.
- A lot of mistakes are visible simply by eye. Have you ever worked an S41 or SH8? Probably not, but SV1 or S58 are quite common.
- Listen carefully to the exchange. Yes, your logging program is offering exchange received in previous contact on another band, but what if it is wrong? In several cases some stations logged the same district for an OK/OM station three times on three different bands but this district was wrong.
- Valid contact requires to receive valid exchange. If the rules say exchange is RTS+nr, then RST+US state is not valid exchange.
If you look at the results, you can see also the percentage of lost QSOs and the total score reduction. At the first sight seems that the non OK/OM ops are more accurate than the OK/OM ops. But you can’t compare these numbers, because the conditions on these two sides are different:
- OK/OM ops are running 99% of the contest, non OK/OM ops are S&P 99% of the contest. The probability of an error is higher when you run a pile-up than if you S&P.
- Non OK/OM ops work only OK/OM stations so they know nearly 50% of a call-sign prior even hearing single dot of it. OK/OM ops are called by stations from the whole world, so the probability of a call-sign error is higher.
- To catch a fixed district code is easier than to catch a serial number.

Valid HTML 4.01!
Copyleft OK1HRA