Untitled

Scoring and the Master Callsign Database

The WT4I Contest Tools have been designed to give the Contest Manager much freedom in choosing how a contest is scored. As such, there are several configurable options dealing with the scoring and the master callsign database. The following paragraphs attempt to describe each scoring option and provide master callsign database build suggestions to help the Contest Manager get the most fair and accurate results.
Each Contest Manager should read and understand the recommendations provided for the scoring options and then make their own determination as to what is appropriate for their contest.


Definitions:

Unique - Any callsign not found in the master callsign database.

Unique +1 - A callsign that can be logically derived from a unique (not in master) callsign by changing or adding a single character in a call. For example WT4II, MT4I, and WT4K will all map to WT4I with Unique +1 processing.


Using the Log versus using the Master:

Under the WT4I Log Checker configuration menu item, the user can chose to perform Unique +1 processing against the log or against the master call database. In either case, a callsign is determined to be unique by not being in the master call database.
If the option is set to use the log, the unique callsign is compared against other callsigns in the log for possible matches. This option is primarily for the individual contestor. Consider the example where WT4I is worked 4 times and the log also contains a KT4I. Assume KT4I is unique (not in master). The unique +1 processing will identify KT4I as unique with an alternate (WT4I). The alternate will have been found by comparing the unique callsign against the log itself.
If the option is set to use the master callsign database, the unique callsign is compared against other callsigns in the master callsign database. This option is dangerous for the individual contester (hence the warning delivered by the program) in that it is very likely to match up with call signs in the master call database that were not in the contest!
The option to use the master call sign database is primarily for official contest log checkers that have built a master call database from the logs received. A master call sign database built from the logs received will only contain callsigns that were highly likely to be in the contest. While a generic master callsign database may have tens of thousands of callsigns, the master built from the logs will typically have only a few thousand (depending on the size of the contest).


Scoring:

Under the WT4I Log Checker configuration menu item, there is the option to change colors and scoring. Here are the description of each of the possible options and a recommendation for scoring:
Normal Text - A good QSO with no flags. The color can be changed but these QSOs are always included in the score.
Not in Master Call Database - (Also known as Unique) These are QSOs that have callsigns that were not found in the master callsign database. They also did not have a valid Unique plus one alternate. While the option exists, it is highly recommended that these QSOs are NOT excluded from the score. This gives the benefit of the doubt to the contestor for true uniques.
QSO is Bad or Invalid - QSOs flagged this way have a busted or callsign that will not map to a country using the cty.dat file. Additionally, callsigns that are found in the badcalls.dat file will be flagged bad. These QSOs are bad and will always be excluded from the scoring.
QSO is a Dupe - For most contests, this means that the QSO was worked twice on one band. For at least one contest, this means that the QSO was worked twice in the same contest. Dupes are excluded from the score.
QSO is Excluded from Log - The QSO has been manually flagged to be excluded from the log and therefore is not included in the score. (The QSO will be removed from the log if the log is saved.)
QSO has Zone Inconsistencies - Specific to the CQ WW contest. The zone logged is inconsistent with the zone that is derived from the cty.dat and zone override files. The user has the option to exclude these QSOs from the score.
QSO has Bad Exchange - Varies from contest to contest. This flag will be set if the exchange is missing. For a contest that exchanges state or province, the log checking software will set this flag if the exchange does not match a valid state or province as found in the .dat file. QSOs with bad exchanges are always excluded from the score.
Call is Unique, has Alternate - The call sign of the QSO was not found in the master call sign database. Additionally a possible valid alternate was found using the unique plus one processing. If used against a very accurate master call sign database, there is a very high probability that the call was copied wrong. The user has the option to exclude these QSOs from the scoring. It is recommended that these QSOs be excluded from the scoring.
Call is Unique, Cross Checked - The call sign of the QSO was not found in the master call sign database. Additionally a possible valid alternate was found using the unique plus one processing. Finally, the alternate was confirmed by *cross checking against the alternate's log. This QSO is extremely likely to have a mis-copied callsign. The user has the option to exclude these QSOs from the scoring. It is recommended that these QSOs be excluded from the scoring.
QSO is Flagged Bad by Checker - The QSO was flagged bad by the log checker. The log checker had the option of adding a comment. This comment is stored and preserved in a file outside the actual log. The user (log checker) has the option to exclude these QSOs from the scoring. It is recommended that these QSOs be excluded from the scoring.
QSO is Not in Log - The QSO was found to be not in the other contestors log. This is determined by *cross checking. The user (log checker) has the option to exclude these QSOs from the scoring. It is recommended that these QSOs NOT be excluded from the scoring.

*Note: The tools to perform cross checking are only available to "Official Contest Managers."


Building and Accurate Master Call Sign Database:

With the ability to exclude QSOs based on unique plus one processing, it is recommended that time and thought be put into building the an accurate master call sign database. Here are my recommendations:
1. Build the master call sign database from all the logs after the final submission date has been reached. The more logs used, the more accurate the master call sign database produced. Encourage all contestants to turn in a log no mater how small.
2. Depending on the size of the contest, choose the number of occurrences to be included. The Master Call Maintenance program will count each callsign only once per log. For a large contest, occurrences greater than equal to 3 may work well. This means that at least three contestors claimed to have worked the station. This could be that 3 stations busted the call the same way or that the station actually existed. In any event, the benefit of the doubt goes to the contestor.
3. Scan the list for obvious busted calls (i.e. DA2OOO vs DA2000). Remove the busted calls by unchecking the entry or add the bad call to the badcalls.dat file.
4. Include the callsigns of the actual entries. If you make a list of every log submitted with one call per line, this can be directly read into Master Call Maintenance as a master call file (provided the extension is .cal).
5. Save and name the master call something meaningful (WPX_2001.cal). Make sure to remember to point the log checking software at the proper master call sign database built for the contest.

	The WT4I Contest Tools have been designed to give the Contest Manager much freedom in choosing how a contest is scored. As such, there are several configurable options dealing with the scoring and the master callsign database. The following paragraphs attempt to describe each scoring option and provide master callsign database build suggestions to help the Contest Manager get the most fair and accurate results. Each Contest Manager should read and understand the recommendations provided for the scoring options and then make their own determination as to what is appropriate for their contest.
	Definitions:
	Unique - Any callsign not found in the master callsign database. Unique +1 - A callsign that can be logically derived from a unique (not in master) callsign by changing or adding a single character in a call. For example WT4II, MT4I, and WT4K will all map to WT4I with Unique +1 processing.
	Using the Log versus using the Master:
	Under the WT4I Log Checker configuration menu item, the user can chose to perform Unique +1 processing against the log or against the master call database. In either case, a callsign is determined to be unique by not being in the master call database. If the option is set to use the log, the unique callsign is compared against other callsigns in the log for possible matches. This option is primarily for the individual contestor. Consider the example where WT4I is worked 4 times and the log also contains a KT4I. Assume KT4I is unique (not in master). The unique +1 processing will identify KT4I as unique with an alternate (WT4I). The alternate will have been found by comparing the unique callsign against the log itself. If the option is set to use the master callsign database, the unique callsign is compared against other callsigns in the master callsign database. This option is dangerous for the individual contester (hence the warning delivered by the program) in that it is very likely to match up with call signs in the master call database that were not in the contest! The option to use the master call sign database is primarily for official contest log checkers that have built a master call database from the logs received. A master call sign database built from the logs received will only contain callsigns that were highly likely to be in the contest. While a generic master callsign database may have tens of thousands of callsigns, the master built from the logs will typically have only a few thousand (depending on the size of the contest).
	Scoring:
	Under the WT4I Log Checker configuration menu item, there is the option to change colors and scoring. Here are the description of each of the possible options and a recommendation for scoring: Normal Text - A good QSO with no flags. The color can be changed but these QSOs are always included in the score. Not in Master Call Database - (Also known as Unique) These are QSOs that have callsigns that were not found in the master callsign database. They also did not have a valid Unique plus one alternate. While the option exists, it is highly recommended that these QSOs are NOT excluded from the score. This gives the benefit of the doubt to the contestor for true uniques. QSO is Bad or Invalid - QSOs flagged this way have a busted or callsign that will not map to a country using the cty.dat file. Additionally, callsigns that are found in the badcalls.dat file will be flagged bad. These QSOs are bad and will always be excluded from the scoring. QSO is a Dupe - For most contests, this means that the QSO was worked twice on one band. For at least one contest, this means that the QSO was worked twice in the same contest. Dupes are excluded from the score. QSO is Excluded from Log - The QSO has been manually flagged to be excluded from the log and therefore is not included in the score. (The QSO will be removed from the log if the log is saved.) QSO has Zone Inconsistencies - Specific to the CQ WW contest. The zone logged is inconsistent with the zone that is derived from the cty.dat and zone override files. The user has the option to exclude these QSOs from the score. QSO has Bad Exchange - Varies from contest to contest. This flag will be set if the exchange is missing. For a contest that exchanges state or province, the log checking software will set this flag if the exchange does not match a valid state or province as found in the .dat file. QSOs with bad exchanges are always excluded from the score. Call is Unique, has Alternate - The call sign of the QSO was not found in the master call sign database. Additionally a possible valid alternate was found using the unique plus one processing. If used against a very accurate master call sign database, there is a very high probability that the call was copied wrong. The user has the option to exclude these QSOs from the scoring. It is recommended that these QSOs be excluded from the scoring. Call is Unique, Cross Checked - The call sign of the QSO was not found in the master call sign database. Additionally a possible valid alternate was found using the unique plus one processing. Finally, the alternate was confirmed by cross checking against the alternate's log. This QSO is extremely likely to have a mis-copied callsign. The user has the option to exclude these QSOs from the scoring. It is recommended that these QSOs be excluded from the scoring. QSO is Flagged Bad by Checker* - The QSO was flagged bad by the log checker. The log checker had the option of adding a comment. This comment is stored and preserved in a file outside the actual log. The user (log checker) has the option to exclude these QSOs from the scoring. It is recommended that these QSOs be excluded from the scoring. QSO is Not in Log - The QSO was found to be not in the other contestors log. This is determined by *cross checking. The user (log checker) has the option to exclude these QSOs from the scoring. It is recommended that these QSOs NOT be excluded from the scoring.
	*Note: The tools to perform cross checking are only available to "Official Contest Managers."
	Building and Accurate Master Call Sign Database:
	With the ability to exclude QSOs based on unique plus one processing, it is recommended that time and thought be put into building the an accurate master call sign database. Here are my recommendations: 1. Build the master call sign database from all the logs after the final submission date has been reached. The more logs used, the more accurate the master call sign database produced. Encourage all contestants to turn in a log no mater how small. 2. Depending on the size of the contest, choose the number of occurrences to be included. The Master Call Maintenance program will count each callsign only once per log. For a large contest, occurrences greater than equal to 3 may work well. This means that at least three contestors claimed to have worked the station. This could be that 3 stations busted the call the same way or that the station actually existed. In any event, the benefit of the doubt goes to the contestor. 3. Scan the list for obvious busted calls (i.e. DA2OOO vs DA2000). Remove the busted calls by unchecking the entry or add the bad call to the badcalls.dat file. 4. Include the callsigns of the actual entries. If you make a list of every log submitted with one call per line, this can be directly read into Master Call Maintenance as a master call file (provided the extension is .cal). 5. Save and name the master call something meaningful (WPX_2001.cal). Make sure to remember to point the log checking software at the proper master call sign database built for the contest.

Scoring and the Master Callsign Database

Copyright © 2001 by Bruce Lifter, WT4I

`Copyright © 2001 by Bruce Lifter, WT4I`