Contest definition

From DXLog.net
Revision as of 14:12, 14 May 2020 by Sm7iun (talk | contribs) (Introduction)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Introduction

Contest rules vary greatly and are typically defined by the contest organizers.
The differences can be in points per QSO, multiplier determination and calculations etc.
To support a wide variety of rules and to allow for easy adding/changing of contest rules in DXLog,
contest rules are defined and controlled through a contest config file.

Contest config files are "semi human readable", plain text files located in the Contest sub-folder in
DXLog's installation folder. A wide range of contest definition files are included in the DXLog standard installation.
The contest config files in the protected installation folder are however not intended for editing or modification
For this, there is a copy of the folder in Windows' unprotected AppData folder structure.
Since this is a hidden folder, a drop down menu item is provided for easy access. (File | Open configuration directory)

Each time DXLog is started, the content of the installation sub-folder and the AppData sub-folder is compared.
If a contest config file in the installation sub-folder is newer than its copy in the AppData sub-folder
(e.g. due to it being updated as part of a new DXLog release), the AppData file is overwritten.

In the opposite case (e.g. due to own modifications of a contest config file), the AppData file remains unchanged.
This means that any modifications of existing contest config files should be done in the AppData folder, but that
such modifications may be overwritten if a newer version is distributed in a later DXLog release.
To secure that a contest config file is not overwritten by future DXLog releases, create a file with a new name.
The same mechanic, with a master folder and an AppData copy, applies to data base (i.e. pre-fill or call history) files.

If you have developed a contest config file that is proven to be correct and that could be useful others, Please contact
the development team to discuss adding it to DXLog's standard contest repertoire.


Configurationpaneltagged3.png
Relation between configuration keys and macros and their related text boxes and drop down menus in the contest configuration panel.

File structure

Each line in a contest definition file usually contains KEY + VALUE pairs. The pair is always separated by the "=" sign. For example:

CONTESTNAME=9A CW

This means the field key is CONTESTNAME and the field value is 9A CW.

Regular expressions

You will see that in many cases DXLog is using regular expressions to verify condition validation and process entries.

For example, regular expressions are used to check if the user keyboard entry is valid against a condition or
set of conditions, for QSO points calculations etc.

Regular expressions in the contest configuration file can be defined as fixed values, but they can
also compare QSO data against fixed values.

Example: We want to validate the user entered data in some of the fields. For example, we want
to validate that the user is allowed to enter NY, FL, GA, or DX in the EXCHANGE field on the contest
configuration screen.

The contest configuration key for this operation is: CFG_MULT_RGX_CHECK.

So to create a validation, as per the previous example, we need the following definition
in the contest config file:


CFG_MULT_RGX_CHECK=^NY$|^FL$|^GA$|^DX$

^ in expression denotes start of the string value
$ in expression denotes end of string value
| in expression is the logical or operation


QSO data is addressed using a origin key (CONFIG, SOURCE, or DEST) and a content key (CALLSIGN, EXCHANGE, DXCC, etc.).
They are combined using "->". Examples of QSO data keys are CONFIG->POWER, SOURCE->DXCC, and DEST->RCVD.

Not all possible combinations of origin keys and content keys are valid. Please see below for valid combinations.

Available origin keys
CONFIG Information originating from contest configuration panel.
SOURCE Information relating to own station.
DEST Information relating to other station.
Available content keys
->CONT Continent
->DXCC DXCC
->CALL or ->CALLSIGN Callsign
->PFX or ->WPX Callsign prefix per WPX definition
->RCVD First element in the received contest exchange.
->RECINFO Second element in the received contest exchange.
->RECINFO2 Third element in the received contest exchange.
->RECINFO3 Fourth element in the received contest exchange.
->EXCHANGE The content of the contest exchange field in the contest configuration panel
->CQZONE WAZ/CQ Zone.
->ITUZONE ITU zone.
->TIME_HOUR The hour of the QSO time as a string with values from "0" to "23".
->PFX_AREA The callsign prefix formatted as main DXCC prefix plus "." and the prefix digit. E.g. "SM.0" or "EA.7".
->OPNAME The content of the operator name field in the contest configuration panel
->POWER The content of the power field in the contest configuration panel

Available combinations of origin and content keys

CONFIG SOURCE DEST
CALLSIGN/CALL CALLSIGN/CALL
CQZONE CQZONE
ITUZONE ITUZONE
CONT CONT
PFX/WPX PFX/WPX
DXCC DXCC
PFX_AREA PFX_AREA
EXCHANGE TIME_HOUR
OPNAME RCVD
POWER RECINFO
RECINFO2
RECINFO3

Example: We want to validate a value which could change on each entry into the log.

For example, we want to calculate points for each QSO with the same country, on the 160m band, in the CW and SSB mode, with 1 point.

The relevant contest configuration key for QSO points calculation is POINTS_FIELD_BAND_MODE.
To create the calculation, as per the previous example, we need the following definition in the contest config file:


POINTS_FIELD_BAND_MODE=SOURCE->DXCC:DEST->DXCC;ALL;^160$;^CW$|^SSB$;1


We can read this definition in the following way:
If the SOURCE (our) DXCC is the same as DEST (other station) DXCC and the
band is 160 and the mode is CW or SSB then the QSO is worth 1 point. In the above definition notice
the SOURCE and DEST keys. We can also use the CONFIG key.

Functions and FX expressions

Some keys allow not only keywords but also functions as arguments.

Functions follow C# syntax and have access to all string, number, and boolean manipulation functions in the language plus a number of helper functions.

The keywords available for regular expressions (see above) area also available in functions.

Some keywords assume an expression that returns a string, like MULT1_FX, WINDOWS_CML_LIST_FX, and FIELD_RCVD_CHECK_FORMAT_FX.

Examples:
MULT1_FX=$FIELDVALUE.Substring(0,4)
MULT1_FX=$FIELDVALUE.Substring(0,$FIELDVALUE.IndexOf('/'))

The first example picks the first four characters in the string as multiplier.
The second example picks the string following the first slash ("/") character as multiplier.
Two variables are available: $FIELDVALUE which is the multiplier itself, and $CALLSIGN which is the other station's call.

The available helper string functions are:

Helpers.GetLastLetter($CALLSIGN) - Returns the last character in the callsign
Helpers.GetPureCall($CALLSIGN) - Returns the callsign without prefix, slashes, etc.
Helpers.GetPrefixArea($FIELDVALUE, $CALLSIGN) - Returns the prefix area as NN.0
Helpers.GetPrefixAreaVEGeo($FIELDVALUE, $CALLSIGN) - Returns the prefix area as NN.0 but treats all Canadian calls as VE

Some keywords assume an expression returning a number, such as SCORE_TOTAL_FX and POINTS_CALC_F.

Other keys assume a boolean expression which can be either a regular expression (as described above) or an FX() expression.
Examples are FIELD_RCVD_FX_CHECK and the first argument of MULT1_EXCEPTION.

Examples:
MULT1_EXCEPTION=FX(Helpers.GetLastLetter("CONFIG->CALLSIGN").Equals(Helpers.GetLastLetter("DEST->CALL")));NONE
MULT1_EXCEPTION=FX(("CONFIG->CALLSIGN").Substring(0,3).Equals(("DEST->CALL").Substring(0,3)));NONE

The first example does not count the QSO as a multiplier if the last letter is the same in the station's callsign and own callsign.
The second example does not count the QSO as a multiplier if the first three characters is the same in the station's callsign and own callsign.

The available boolean helper functions are:

Helpers.Between(number, min, max) - Returns true if number is between min and max.

General contest description keys

These keys are used for general contest description in the contest config file, such as the contest name, link to the rules etc.
CONTESTGROUP Used for group contest when displaying the config screen for contest selection. For example: DIGITAL MODES, 9A LOCAL CONTEST, etc.
CONTESTNAME The contest name as it will be shown and recognized in the contest selection box.
Note: this can be same as the Cabrillo contest name, but usually it is the full contest name.
This field is mandatory and must be unique for all files in contest definition folder.
CONTESTEXCH Web link to definition of contest exchange. Shown when entering invalid data in configuration panel's exchange field. e.g. https://www.iota-world.org/
CONTESTRULES External HTTP Link to contest rules. Adds "Contest rules" item to Help menu. e.g. https://www.cqww.com/rules.htm
CONTESTWEB External HTTP Link to contest rules. Adds "Contest web" item to Help menu. e.g. https://www.cqww.com

Contest configuration panel control keys

These keys are used for setting the contest configuration variables in the user configuration window.
CATEGORIES Semicolon-separated list of contest categories shown in the category selection dropdown
menu in the contest configuration panel.
NB. When defining own categories, the values of CABRILLO_OPERATOR, CABRILLO_TRANSMITTERS,
and CABRILLO_ASSISTED may have to be changed from their defaults.
C.f the Cabrillo section below.
Default value: Single operator;Single operator assisted;
Multioperator, single transmitter;Multioperator, two transmitter;
Multi operator, multi-transmitter
CATEGORY_MODES Semicolon-separated list of contest modes shown in the mode selection
dropdown menu in the contest configuration panel.
NB. There is no contest mode key for Cabrillo export. The
category mode string (in upper case) is also used for Cabrillo export.
Default value: CW;SSB;Mixed
CLASS Semicolon-separated list of contest classes shown in the class selection
dropdown menu in the contest configuration panel.
Default value: High;Low;QRP
OVERLAY Semicolon-separated list of contest overlays shown in the overlay selection
dropdown menu in the contest configuration panel.
Default value: ---;Band restricted;Radio Club;Dxpedition;
Headquarters; Open;Restricted;Novice;
Classic;Rookie;Tribander/Single element;
QRP;Fixed station;Portable station
CFG_MULT Controls the use of the exchange field in contest configuration panel. Valid values are: ON and OFF.
If OFF, the exchange field is greyed out.
Default value: OFF
CFG_MULT_DX_ALLOWED Controls if "DX" is an acceptable entry in exchange field. For example in ARRL DX Contest, all USA/VE stations
needs to enter their state/province, while all other stations enters DX here.
Valid values are: YES and NO
Default value: NO
CFG_MULT_SLASH_ALLOWED Controls if "/" is acceptable as part of entry in exchange field.
Used as separator in contests with multi-part exchange multipliers.
Valid values are: YES and NO
Default value: NO
CFG_MULT_MANDATORY Controls if the exchange field requires an entry or can be empty. Valid values are: YES and NO Default value: NO
CFG_MULT_ERRORTEXT Defines error text which is shown if the validity test for the exchange field fails.
For example, in ARRL DX Contest, if the user enters a state abbreviation which is not in the approved list.
Default value: "Invalid value in exchange field!"
CFG_MULT_FROM=CUSTOM_MULT_LIST Alternative to using a regular expression to check validity of entry in Exhange field. Default value: Unused
CFG_MULT_RGX_CHECK Regular expression used to test validity of entry in Exchange field.
Note that the regular expression can include the key CUSTOM_MULT_LIST
meaning that any entry listed in the custom multiplier list is considered valid.
Example: CFG_MULT_RGX_CHECK=^AF$|^AS$|^EU$|^NA$|^OC$|^SA$|CUSTOM_MULT_LIST
Default value: ALL
CFG_CQZONE_ERRORTEXT Defines the error text shown if the entry in the WAZ field fails the validity test. Default value: "Invalid CQ/WAZ zone!"
CFG_CQZONE_MANDATORY Controls if the WAZ field requires an entry or can be empty. Valid values are: YES and NO Default value: NO
CFG_GRID_ERRORTEXT Defines the error text shown if the entry in the GRIDSQUARE field fails the validity test. Default value: "Invalid entry in gridsquare field!"
CFG_GRID_MANDATORY Controls if the GRIDSQUARE field requires an entry or can be blank. Valid values are: YES and NO Default value: NO
CFG_GRID_RGX_CHECK Regular expression used to test validity of data entered in the GRIDSQUARE field. Default value: ALL
CFG_ITUZONE_ERRORTEXT Defines error text shown if the entry in the ITU zone field fails the validity test. Default value: "Invalid ITU zone!"
CFG_ITUZONE_MANDATORY Controls if the ITU requires an entry or can be empty. Valid values are: YES and NO Default value: NO
CFG_MYDXCC_ERRORTEXT Defines the error text shown if the entry in the DXCC field fails the validity test. Default value: "Unrecognized DXCC from DXCC field.
Please enter valid country prefix in DXCC field"
CFG_MYDXCC_MANDATORY Controls if the DXCC field requires an entry or can be empty. Valid values are: YES and NO Default value: NO
CFG_OPNAME_ERRORTEXT Defines the error text shown if the entry in the operator name field fails the validity test. Default value: "Operator name field is mandatory!"
CFG_OPNAME_MANDATORY Controls if the operator name field requires an entry or can be empty. Valid values are: YES and NO Default value: NO
CFG_POWER_ERRORTEXT Defines the error text shown if the entry in the power field fails the validity test. Default value: "Invalid value in power field!"
CFG_POWER_MANDATORY Controls if the power field requires an entry or can be empty. Valid values are: YES and NO Default value: NO
CFG_POWER_RGX_CHECK Regular expression used to determine the validity of the power field entry. Default value: ALL
CFG_STATE_ERRORTEXT Defines the error text shown if the entry in the state/province/other field fails the validity test. Default value: "Invalid value in state/other field!"
CFG_STATE_FROM=CUSTOM_MULT_LIST Defines a list-based validity test for the state/province/other field. Alternative to to using a regular expression. Default value: absent
CFG_STATE_MANDATORY Controls if the state/province/other field requires an entry or can be empty. Valid values are: YES and NO Default value: NO
CFG_STATE_RGX_CHECK Regular expression used to test validity of entry in state/province/other field.
Note that the regular expression can include the key CUSTOM_MULT_LIST
meaning that any entry listed in the custom multiplier list is considered valid.
Example: CFG_STATE_RGX_CHECK=^YL$|^OM$|CUSTOM_MULT_LIST
Default value: ALL

Cabrillo export keys

These keys are used for configuring the Cabrillo export. DXLog only exports Cabrillo 3.0.
CABRILLO_ASSISTED Semicolon-separated list of mapping of categories to Cabrillo assistance types.
MUST have the same number of entries as the defined contest categories.
Valid list items are ASSISTED and NON-ASSISTED.
Default value:
NON-ASSISTED;ASSISTED;
ASSISTED;ASSISTED;ASSISTED
CABRILLO_ASSISTED_DISABLED No CATEGORY-ASSISTED line will be included in exported file. Default value: NO.
CABRILLO_BAND Semicolon-separated list of frequency definition for contests with band-limited categories.
MUST have the same number of entries as the contest's category if defined.
Defaults to all
CABRILLO_CONTEST_NAME Formal contest name for Cabrillo export. No default value
CABRILLO_DEF_RECINFO Value to use for RECINFO field in Cabrillo export if empty. Default value: Empty
CABRILLO_DEF_RECINFO2 Value to use for RECINFO2 field in Cabrillo export if empty. Default value: Empty
CABRILLO_DEF_RECINFO3 Value to use for RECINFO3 field in Cabrillo export if empty. Default value: Empty
CABRILLO_DXPEDITION Semicolon-separated list of mapping of contest categories to Cabrillo
CATEGORY-DXPEDITION key. MUST have the same number of entries as the defined
categories. Valid list items are NON-DXPEDITION and EXPEDITION.
If left undefined, this category
is not included in Cabrillo export.
CABRILLO_LINE USE:
CABRILLO_LINE=FREQ{F=R,6, };MODE{F=L,2, };DATE;TIME;MYCALL{F=L,13, };SENT{F=L,3, };NR{F=R,3,0,4}

Data is taken from the field names and added to the Cabrillo line in the
order entered. FREQ represents frequency of QSO, MODE represents mode etc.
Formatting information is contained within the {}
F= is the formatting call and should be followed by the following parameters:
Alignment: L(eft), R(ight)
Padded size for alignment. Total size of formatted element including padding character.
Padding character: Which character will be used for filling empty spaces.
Total size of the field in the Cabrillo line including space padding. Optional.
Example: RCVD2{F=R,3,0,4}
The RCVD2 field value will be aligned Right, to a length of 3 characters.
The "0" character is used to pad to the specified length.
Total size will be 4 characters (padding with space to reach 4).
This means that if RCVD2 field value is "1", it will be formatted as " 001"
in the Cabrillo QSO line.
Valid keywords are: FREQ, MODE, DATE, TIME, MYCALL, NR, SENT (sent RST),
MULTSENT, CALL, RCVD1 (received RST), RCVD2, RECINFO, RECINFO2, CALL,
EXCHANGE, and OPNAME.
It is also possible to use regular expressions in the line by preceeding them with "*RGX:".

No default value
CABRILLO_LOCATION_CHECK Regular expression that checks the entered location for validity when prompted. Default value: Empty
CABRILLO_LOCATION_DEFAULT Default value of geographical location for Cabrillo export when prompted. No default value
CABRILLO_LOCATION_PROMPT Regular expression that controls for if user is prompted for location information at Cabrillo export. Default value: Empty
CABRILLO_MODES Semicolon-separated list of mapping of the contest's modes (as defined by the MODES key) to Cabrillo modes in QSO lines.
MUST have the same number of entries as the defined number of modes for the contest.
Valid list items are CW, PH, DG, RY, and FM. Some contests use non-standard keys such as PS.
Default value: CW;PH
CABRILLO_OPERATOR Semicolon-separated list of mapping of categories to to Cabrillo operator count.
MUST have the same number of entries as the defined categories.
Valid list items are SINGLE-OP, MULTI-OP, and CHECKLOG.
Default value:
SINGLE-OP;SINGLE-OP;
MULTI-OP;MULTI-OP;MULTI-OP
CABRILLO_OVERLAY Semicolon-separated list of mapping of category overlays to Cabrillo overlays.
MUST have the same number of entries as the defined overlays.
Any string is a valid entry.
Default value:
;BAND RESTRICTED;RADIO CLUB;
DXPEDITION;HEADQUARTERS;
OPEN;RESTRICTED;NOVICE;
CLASSIC;ROOKIE;TB-WIRES;
QRP;FIXED STATION;PORTABLE STATION
CABRILLO_OVERLAY_DISABLED No OVERLAY line will be included in exported file. Default value: NO.
CABRILLO_POWER Semicolon-separated list of mapping of category power classes to Cabrillo power classes.
MUST have the same number of entries as the contest's power classes.
Valid list items are HIGH, LOW, and QRP.
Default value: HIGH;LOW;QRP
CABRILLO_QTC_LINE Definition of Cabrillo output for QTC. C.f. CABRILLO_LINE No default value
CABRILLO_TIME Semicolon-separated list of duration for each contest category.
MUST have the same number of entries as there are contest categories.
No default value
CABRILLO_TRANSMITTER Semicolon-separated list of mapping of categories to Cabrillo operator counts.
MUST have the same number of entries as contest categories.
Valid list items are ONE, TWO, LIMITED, UNLIMITED, and SWL.
Default value:
ONE;ONE;ONE;TWO;UNLIMITED

Band and mode keys


BANDS A semicolon-separated list of available bands for the contest. Default value: 160;80;40;20;15;10
MODES A semicolon-separated list of modes usable for the contest.
Not to be confused with CATEGORY_MODES.
Default value: CW;SSB
EDI_BANDS A semicolon-separated list of EDI values for bands specified in BANDS key.
Must contain same number of entries as BANDS key.
Used for generating EDI log files for VHF/UHF/SHF contests in IARU Region I.
Valid values are: 28 MHz, 50 MHz, 70 MHz, 144 MHz, 432 MHz, 1,3 GHz, 2,3 GHz,
3,4 GHz, 5,7 GHz, 10 GHz, 24 GHz, 47 GHz, 76 GHz, 120 GHz, 144 GHz, and 248 GHz.
Note the space between the number and the frequency multiplier and that
commma is used as decimal separator.
No default value which
means EDI export is disabled.

Configuration keys' relation to Cabrillo export

Relation between contest category configuration and Cabrillo export
Key type DXLog Key Cabrillo key Default values
Configuration CATEGORIES Single operator Single operator assisted Multioperator, single transmitter Multioperator, two transmitter Multi operator, multi-transmitter
Cabrillo CABRILLO_OPERATOR CATEGORY-OPERATOR SINGLE-OP SINGLE-OP MULTI-OP MULTI-OP MULTI-OP
Cabrillo CABRILLO_TRANSMITTER CATEGORY-TRANSMITTER ONE ONE ONE TWO UNLIMITED
Cabrillo CABRILLO_ASSISTED CATEGORY-ASSISTED UNASSISTED ASSISTED ASSISTED ASSISTED ASSISTED
Cabrillo CABRILLO_BAND CATEGORY-BAND ALL ALL ALL ALL ALL
Relation between contest overlay configuration and Cabrillo export
Key type DXLog Key Cabrillo key Default values
Configuration OVERLAY --- Band restricted Radio Club Dxpedition ...
Cabrillo CABRILLO_OVERLAY CATEGORY-OVERLAY BAND RESTRICTED RADIO CLUB DXPEDITION ...
Relation between contest power class configuration and Cabrillo export
Key type DXLog Key Cabrillo key Default values
Configuration CLASS High Low QRP
Cabrillo CABRILLO_POWER CATEGORY-POWER HIGH LOW QRP
Relation between contest mode categories and Cabrillo export
Key type DXLog Key Cabrillo key Default values
Configuration CATEGORY_MODES CW SSB Mixed
Cabrillo N/A CATEGORY-MODE Value is determined automatically by capitalizing contest mode from configuration.
Relation between available contest QSO modes and Cabrillo export
Key type DXLog Key Cabrillo key Default values
Configuration MODES CW SSB
Cabrillo CABRILLO_MODES QSO CW PH
Relation between contest band category and Cabrillo export
Key type DXLog Key Cabrillo key Default values
Configuration BANDS 160 80 40 20 15 10
Cabrillo N/A CATEGORY-BAND Value is determined automatically. If log contains QSO on only one band, this is used. Otherwise value defaults to ALL.

Entry field definition keys

These keys are used to control the layout of QSO entry fields. The keys set the visibility, length, labels, checking procedures etc.
for each of the fields which the user can enter data or display for any QSO.
FIELD_AZ_VISIBLE Controls the visibility of the Azimuth field.
Mostly used on VHF/UHF/SHF to get the azimuth angle from a gridsquare.
Valid values are YES and NO.
Default value: NO
FIELD_CALLSIGN_WWL_CHECK If YES, an entry in the log callsign field will be checked for a gridsquare entry.
If a gridsquare is found, the callsign field value will be copied to the gridsquare
entry field and the azimuth angle will be calculated and shown.
Valid values are YES and NO.
Default value: NO
FIELD_MODE_VISIBLE Mode field visible on the QSO entry line. Valid values are YES and NO. Default value: NO
FIELD_MODE_NAME Heading for mode column. Default value: "Mode"
FIELD_MULT_NAME Heading for multiplier column. Default value: "Mult"
FIELD_MULT_VISIBLE If MULT field is visible on the screen. Valid values are YES and NO. Default value: NO
FIELD_MULT_MAX_LENGTH Width of MULT column. Default value: 5
FIELD_NR_VISIBLE If sent QSO SERIAL NUMBER is visible on the QSO entry line.
Valid values are YES and NO.
Default value: NO
FIELD_NR_HIDDEN_DXCC Semicolon separated list of DXCC. If our own DXCC is on this list,
sent serial number field will be hidden. Useful for contests where some
stations are sending a serial number exchange and other stations are
sending other data (for example a local province).
Default is to hide none
FIELD_NR_HIDDEN_RGX Regular expression. If the condition is valid, sent serial number
field will be hidden. Useful for contests where some stations are sending
a serial number exchange and other stations are sending other data
(for example a local province).
No default value
FIELD_PERIOD_VISIBLE If PERIOD number column is visible. Valid values: YES and NO. Default value: NO
FIELD_PERIOD_NAME Heading for PERIOD number column. Default value: "P"
FIELD_PTS_VISIBLE If POINTS column is visible. Valid values: YES and NO. Default value: NO
FIELD_PTS_NAME Heading for POINTS column. Default value: "Pts"
FIELD_RCVD_CHECK_FORMAT_FX
FIELD_RECINFO_CHECK_FORMAT_FX
FIELD_RECINFO2_CHECK_FORMAT_FX
FIELD_RECINFO3_CHECK_FORMAT_FX
C# expression to reformat entered value in the field before further
validity checking. The value in the field is represented as $FIELDVALUE.
Example:
FIELD_RCVD_CHECK_FORMAT_FX=$FIELDVALUE.Substring(0,2)+$FIELDVALUE.Substring(2).TrimStart('0')
will reshape RCVD by taking the first to characters and then remove any
leading zeroes in the remainder before further validity checking.
Default value: *
FIELD_RCVD_COPY
FIELD_RECINFO_COPY
FIELD_RECINFO2_COPY
FIELD_RECINFO4_COPY
If the field's value is automatically copied from previous QSO with same station.
Valid values: YES and NO.
Default value: NO
FIELD_RCVD_COPY_EXC_DXCC Semicolon separated list DXCC entities for which RCVD is not copied
from earlier QSO. Useful in case when we want to copy value from
previous QSO only for some station.
Default value: NONE
FIELD_RCVD_COPY_EXC_RGX
FIELD_RECINFO_COPY_EXC_RGX
FIELD_RECINFO2_COPY_EXC_RGX
FIELD_RECINFO3_COPY_EXC_RGX
Regular expression. For QSO where the condition is true, the
content of the field will not be copied from earlier QSO.
No default value
FIELD_RCVD_COPY_FX C# expression used to determine value to be copied from earlier QSO.
The value of the field is $FIELDVALUE.
Example:
FIELD_RCVD_COPY_FX=$FIELDVALUE.Substring(0,6)
will copy the first six characters from the RCVD field from the
previous QSO with the same station.
No default value
FIELD_RCVD_DEFAULT_VALUE Value to be used in export if RCVD field is empty.
Valid values are: CQZONE, ITUZONE, CONT, or any string, which will be used verbatim.
No default value
FIELD_RCVD_EXC_CHECK_DXCC List of DXCC countries separated by ":" which are exception for value
checking procedure followed by a definition of the multipliers after ";".
No default value
FIELD_RCVD_FORMAT_FX
FIELD_RECINFO_FORMAT_FX
FIELD_RECINFO2_FORMAT_FX
FIELD_RECINFO3_FORMAT_FX
C# expression used to format entered value before saving. No default value
FIELD_RCVD_FX_CHECK
FIELD_RECINFO_FX_CHECK
FIELD_RECINFO2_FX_CHECK
FIELD_RECINFO3_FX_CHECK
Boolean C# expression used to check if value entered in the field is valid.
Example:
FIELD_RCVD_FX_CHECK=Helpers.Between($FIELDVALUE,1,40)
checks if RCVD is between 1 and 40.
No default value
FIELD_RCVD_MANDATORY
FIELD_RECINFO_MANDATORY
FIELD_RECINFO2_MANDATORY
FIELD_RECINFO3_MANDATORY
If RCVD field entry is mandatory. Valid values are YES and NO. Default value: NO
FIELD_RCVD_MANDATORY_RGX_EXC
FIELD_RECINFO_MANDATORY_RGX_EXC
FIELD_RECINFO2_MANDATORY_RGX_EXC
FIELD_RECINFO3_MANDATORY_RGX_EXC
Defines exceptions from mandating rule via a regular expression.
Example:
FIELD_RCVD_MANDATORY_RGX_EXC=!DEST->DXCC:^G$|^GD$|^GI$|^GJ$|^GM$|^GU$|^GW$
means RCVD is not mandatory for UK stations.
No default value
FIELD_RCVD_MAX_LENGTH
FIELD_RECINFO_MAX_LENGTH
FIELD_RECINFO2_MAX_LENGTH
FIELD_RECINFO3_MAX_LENGTH
Maximum number of characters accepted in the field. Default value: 10
FIELD_RCVD_MIN_LENGTH
FIELD_RECINFO_MIN_LENGTH
FIELD_RECINFO2_MIN_LENGTH
FIELD_RECINFO3_MIN_LENGTH
Minimum number of characters accepted in the field. Default value: 0
FIELD_RCVD_AUTOSKIP Controls whether RCVD and RECINFO fields are treated as one continuous field.
E.g. when typing in the RCVD field, the cursor will automatically skip to the RECINFO
field when the maximum length of the RCVD field is reached.
Also, when deleting characters with [Back], the cursor will automatically move to the previous field.
Only recommended for contests where all exchange elements have a fixed length.
Default value: NO
FIELD_RCVD_NUMERIC
FIELD_RECINFO_NUMERIC
FIELD_RECINFO2_NUMERIC
FIELD_RECINFO3_NUMERIC
Controls if the field accepts only numeric characters.
Valid values are YES and NO.
Default value: NO
FIELD_RCVD_SLASH_ALLOWED
FIELD_RECINFO_SLASH_ALLOWED
FIELD_RECINFO2_SLASH_ALLOWED
FIELD_RECINFO3_SLASH_ALLOWED
Controls if the field accepts a slash "/" character.
Valid values are YES and NO.
Default value: NO
FIELD_RCVD_RGX_CHECK
FIELD_RECINFO_RGX_CHECK
FIELD_RECINFO2_RGX_CHECK
FIELD_RECINFO3_RGX_CHECK
Regular expression. Used to check if entry in the field is valid.
For contests with more than one type of exchange (e.g. grid and serial
number or oblast and grid), more than one rule can be listed, separated
by semicolon. The check is then done against the union of the rules, i.e.
if any of the rules checks OK, the entry is approved.
No default value
FIELD_RCVD_TYPE
FIELD_RECINFO_TYPE
FIELD_RECINFO2_TYPE
FIELD_RECINFO3_TYPE
Defines data type of the field.
Valid values are: GRID, GRID4, NR, CUSTOM,
MULT, CQZONE, ITUZONE, and NAME.
NB. By default, no validity checking is done for types GRID and GRID4 for RCVD,
thus requiring an FIELD_RCVD_RGX_CHECK key if validity checking is wanted.
Default value: Empty
FIELD_RCVD_WWL_CHECK If YES, entry in RCVD field will be checked if it can be possible gridsquare entry.
It it is gridsquare, then RCVD field value will be copied to gridsquare entry field
and Azimuth will be calculated and shown. Valid values are YES and NO.
Default value: NO
FIELD_RECINFO_NAME
FIELD_RECINFO2_NAME
FIELD_RECINFO3_NAME
Heading for field's column. Default value: Empty
FIELD_RECINFO_RGX_SEL_POS
FIELD_RECINFO2_RGX_SEL_POS
FIELD_RECINFO3_RGX_SEL_POS
Filtering function for composite multipliers.
Only FIELD_RECINFO_RGX_SEL_POS is used, in AGCW QRP contest.
No default value
FIELD_RECINFO_VISIBLE
FIELD_RECINFO2_VISIBLE
FIELD_RECINFO3_VISIBLE
Controls if the the field is visible.
Valid values: YES, HIDDEN, and READONLY.
Default value: HIDDEN
FIELD_RST_3RD_LETTER Semicolon-separated list of allowed third characters apart from numbers.
Example:
FIELD_RST_3RD_LETTER=A;S
allows 59A and 59S as reports.
Default value: None
FIELD_RST_VISIBLE Controls visibility of RST field. Valid values are: YES and NO. Default value: YES
FIELD_SENT_VISIBLE Controls visibility of Sent field in log. Valid values are: YES and NO. Default value: YES

Default message keys

Default messages for F-keys, Plus and Ins.
CW_MESSAGE_1 Default F1 message for Run Default value: "CQ $MYCALL $MYCALL TEST"
CW_MESSAGE_2 Default F2 message for Run Default value: "$RST $EXCHANGE"
CW_MESSAGE_3 Default F3 message for Run Default value: "$EXCHANGE"
CW_MESSAGE_4 Default F4 message for Run Default value: "$MYCALL"
CW_MESSAGE_5 Default F5 message for Run Default value: "$LOGGEDCALL"
CW_MESSAGE_6 Default F6 message for Run Default value: "NR?"
CW_MESSAGE_7 Default F7 message for Run Default value: "?"
CW_MESSAGE_INS Default Insert message for Run Default value: "$F2"
CW_MESSAGE_PLUS Default Plus message for Run Default value: "$CORRECT TU $CR $MYCALL"
SP_CW_MESSAGE_1 Default F1 message for S&P Default value: "$MYCALL"
SP_CW_MESSAGE_2 Default F2 message for S&P Default value: "$RST $EXCHANGE"
SP_CW_MESSAGE_3 Default F3 message for S&P Default value: "$EXCHANGE"
SP_CW_MESSAGE_4 Default F4 message for S&P Default value: "$MYCALL"
SP_CW_MESSAGE_5 Default F5 message for S&P Default value: "$LOGGEDCALL"
SP_CW_MESSAGE_6 Default F6 message for S&P Default value: "NR?"
SP_CW_MESSAGE_7 Default F7 message for S&P Default value: "?"
SP_CW_MESSAGE_INS Default Insert message for S&P Default value: "$CR $F2"
SP_CW_MESSAGE_PLUS Default Plus message for S&P Default value: "$CR $TU"
CW_MESSAGE_EXCHANGE_FILTER Message definitions following this key will only be effective if regular expression
after equal sign evaluates true for content in exchange entry box.
Example: CW_MESSAGE_EXCHANGE_FILTER=^DX$
means that messages below this line will be used for stations entering
DX in the exchange entry box.

Special configuration keys

Special configuration keys
DXC_COMMENT_EXTRACT This entry is used to extract exchange or multiplier information from DX cluster comments. For example, the line:
DXC_COMMENT_EXTRACT=RECINFO;(AF|AN|AS|EU|NA|OC|SA)[ /\-\.]?\d{1,3};[ /\-\.]
will extract a typical IOTA designation such as AF-025 and insert it into the RECINFO prefill field for the spot.
The first part of the configuration (before the ;) defines into which entry field the data should be placed.
the second part of the configuration is a regular expression that defines the data that is to be matched.
DXCC_DB_TYPE This entry allows the use of a custom country file (for example, R150S.dat). If a custom country file is defined, the selection
in Option|Data files|Country files will be ignored and the country file defined in the contest config file will be used.
Valid values are: CUSTOM_CTY and CTY
Default value is CTY which will use the data base set
in the Options|Data files|Country files panel.
DXCC_DB_FILENAME Used to enable the use of an alternative country data base. Used in conjunction with the DXCC_DB_TYPE key
to define the data file name. The file format is the same as the normal CTY.DAT file.
Default value: CTY.DAT

Additional configuration keys

BAND_BONUS Semicolon-separated list of band point bonuses (multiplication factors), aligned with band list. Default value: 1 for all used bands
MODE_GROUP Semicolon-separated list of modes. Not used. No default value
DISPLAY_MODE_GROUPING Formatting of display of modes in summary window.
Syntax: DISPLAY_MODE_GROUPING=modename1:mode1+mode2;modename2:mode3+mode4
No default value
MIN_OFF_TIME Minimum time without QSO to count as off time. In minutes. Default value: 30
DXCC_DB_USE_ARRL_LIST Controls the use of the ARRL country list instead of CQ country list. Default value: NO
CONTEST_LENGTH Duration of contest in minutes. No default value
CONTEST_FIRST_HOUR Time of day for start of contest in UTC. Valid formats: H, HH, HMM, and HHMM. No default value
PERIOD Whether the contest has periods. Valid values: ON and OFF. Default value: OFF
PERIOD_LENGTH The length of each contest period in minutes. Valid values: Any integer. Default value: 0
PERIOD_AUTOSWITCH If the next period should start automatically. Valid values: YES and NO. Default value: NO
PERIOD_NUMBER Number of periods in contest. Valid values: CALC_FROM_TIME or any integer.
CALC_FROM_TIME means duration divided by period length.
Default value: 0
PERIOD_MODES Semicolon-separated list of modes for each period in the contest.
Must have the same number of items as number of periods.
No default value
SPRINT_LOGIC_ALLOWED Allow sprint logic. Default value: NO
INITIAL_SERIAL_NUMBER Starting value of sent serial number. Default value: 1
WARNING_FILE Name of frequency range warning file located in %appdata%\DXLog\Database.
The format of each line in the warning file is Mode regular expression;frequency range;Message
Example:
# Format=MODE;FREQ_Range;Warning message
^CW$;3400-3520;Warning: Operation not allowed on this frequency
^CW$;3550-3900;Warning: Operation not allowed on this frequency
^[LUS]SB$;3400-3600;Warning: Operation not allowed on this frequency
^[LUS]SB$;3675-3700;Warning: Operation not allowed on this frequency
^[LUS]SB$;3725-3900;Warning: Operation not allowed on this frequency
No default value
ADIF_KEYS Allows for exporting custom keys in ADIF. The syntax is ADIF_KEYS=ADIFKEY;Expression;Regexp.
Regexp must evaluate as true for the key to be included in the export.
The syntax for Expression is C# and based on internal DXQSO object structure.
Received exchanges are $VALUE.Rcvd, $VALUE.Rcvd4, $VALUE.RecInfo, $VALUE.RecInfo2,
and $VALUE.RecInfo3. Rcvd4 is the Rcvd object without the signal report.
So to, for instance, export the received exchange as US/VE state use ADIF_KEYS=STATE;$VALUE.Rcvd4;.
To export the second part of the exchange as operator name use ADIF_KEYS=NAME;$VALUE.RecInfo;
The following $VALUE.xxx keys are available: Sent, Rcvd, Rcvd4, RecInfo, RecInfo2, RecInfo3,
Mult, Mult1, Mult2, Mult3, Lp, Stn, OriginStndID, Operator,
and RadioVFO.
Please note that you can also use C# style string manipulation such as Substring(start, length) etc.
There is no limit on the number of ADIF_KEYS lines in a contest definition file.
Default value: None
DB_FILE or DB_FILE1
DB_FILE2
DB_FILE3
DB_FILE4
DB_FILE5
File name of prefill data base.
DB_FILE_TYPE or DB_FILE1_TYPE
DB_FILE2_TYPE
DB_FILE3_TYPE
DB_FILE4_TYPE
DB_FILE5_TYPE
Extension of data base file. Default value: .TXT
DB_FILE_COL_RCVD or
DB_FILE1_COL_RCVD
DB_FILE2_COL_RCVD
DB_FILE3_COL_RCVD
DB_FILE4_COL_RCVD
DB_FILE5_COL_RCVD
Column number of RCVD field in data base file.
NB. At least one DB_FILE_COL* statement must be included for each data base file.
NB. Since look-up for RCVD is enabled by default, it needs to
be actively disabled if not wanted. Set it to -1 to disable look-up.
DB_FILE_COL_RECINFO or
DB_FILE1_COL_RECINFO
DB_FILE2_COL_RECINFO
DB_FILE3_COL_RECINFO
DB_FILE4_COL_RECINFO
DB_FILE5_COL_RECINFO
Column number of RECINFO field in data base file.
DB_FILE_COL_RECINFO2 or
DB_FILE1_COL_RECINFO2
DB_FILE2_COL_RECINFO2
DB_FILE3_COL_RECINFO2
DB_FILE4_COL_RECINFO2
DB_FILE5_COL_RECINFO2
Column number of RECINFO2 field in data base file.
DB_FILE_COL_RECINFO3 or
DB_FILE1_COL_RECINFO3
DB_FILE2_COL_RECINFO3
DB_FILE3_COL_RECINFO3
DB_FILE4_COL_RECINFO3
DB_FILE5_COL_RECINFO3
Column number of RECINFO3 field in data base file.
DB_FILE_FILL_FORMAT or
DB_FILE1_FILL_FORMAT
DB_FILE2_FILL_FORMAT
DB_FILE3_FILL_FORMAT
DB_FILE4_FILL_FORMAT
DB_FILE5_FILL_FORMAT
C# expression defining how prefill from data base file will be used.
Example: /{0} will precede prefill with a slash.
This function is often combined with the menu option to use INSERT mode in the RCVD field.
RGX_GUESS_DB Regular expression "rule base" for guessing exchange of unworked stations.
Syntax is RGX_GUESS_DB=Field;Regexp1;Regexp2;Filename
QSO_NUMBER QSO numbering principle.
Valid values: ALL, PER_MODE, PER_BAND, PER_PERIOD, PER_BAND_MODE, PER_PERIOD_MODE.
ALL means chronological numbering.
Default value: ALL
QSO_NUMBER_CATEGORY Semicolon-separated list of numbering principles for each contest category.
Must contain the same number of elements as contest categories.
Valid values: ALL, PER_MODE, PER_BAND, PER_PERIOD, PER_BAND_MODE, PER_PERIOD_MODE.
If not present, the value
of QSO_NUMBER is used.
DOUBLE_QSO The definition of a dupe. Valid values: PER_BAND,
PER_BAND_MODE, PER_PERIOD, PER_MINUTE_DIFFERENCE,
PER_PERIOD_BAND, PER_PERIOD_MODE,
PER_PERIOD_BAND_MODE, PER_BAND_DAY
Required. Lacks default value.
MULT_SUM Summing method for multipliers. Valid values: NO, ALL, PER_BAND, and PER_PERIOD. Default value: ALL
DOUBLE_QSO_MINUTE_DIFFERENCE Minimum time difference to not be counted as a dupe. Used in conjunction with DOUBLE_QSO=PER_MINUTE_DIFFERENCE.
MIN_VALID_QSO_DIFFERENCE Minimum allowed time between QSO with the same station (e.g. on other band or mode). Default value: 0
DOUBLE_QSO_MODE_CHECK Definition of dupe principle when it comes to mode. Valid values: PER_MODE, PER_CABRILLO_MODE, and PER_MODE_GROUP. Default value: PER_MODE
POINTS_TYPE Type of points. Valid values: CALC, QRB, QRB_EXCHANGE+CALCF, QRB+CALCF, RAEM, and FROM_TABLE()
CALC expects the presence of POINTS_FIELD_BAND_MODE keys. QRB means one point per kilometer.
QRB_EXCHANGE+CALCF requires at least one POINTS_CALC_F key and uses a grid in the config's Exchange field for QRB calculation.
QRB+CALCF requires at least one POINTS_CALC_F key and uses the config's Grid field for QRB calculation.
RAEM uses the special RAEM contest point system.
FROM_TABLE(filename;keytype;sourcekey;destkey) requires a text file that maps an exchange value to points, keytype is always INT,
sourcekey is always "EXCHANGE", destkey can be RCVD, RECINFO, RECINFO2, or RECINFO3.
The format of each line in the file is sourcekey value;destkey value=points.
Default value: CALC
SCP_DATABASE_DISABLE Disable check partials database. (for e.g. WRTC). Valid values are: YES and NO. Default value: NO
POINTS_BAND_BONUS Per band scaling factor, often used for VUSHF contests. Syntax POINTS_BAND_BONUS=band;scaling.
Example: POINTS_BAND_BONUS=144;2 doubles the points number on the 2m band.
DXC_COMMENT_EXTRACT Regular expression used to extract mult information from DX cluster spots for highlighting in band map and prefill.
Syntax is DXC_COMMENT_EXTRACT=field;regexp.
Example: DXC_COMMENT_EXTRACT=RECINFO;(AF|AN||AS|EU|NA|OC|SA)[ /\-\.]?\d{1,3};[ /\-\.]
extracts IOTA keys into a RECINFO prefill for the call.
OWN_MULT_VALID Controls if own multiplier is valid. NB. Controls the validity of ALL own multipliers and
does not consider calculated multipliers, e.g. via the MULT1_FX key.
Default value: NO
CUSTOM_MULT_LENGTH Length of an enumerated numeric multiplier. If number is shorter, it is left padded with zeroes.
Used with enumerated multipliers, e.g. "=1-1999".
Default value: 0
RATE_ODX_VISIBLE Show distance statistics in Rate window. Default value: NO
CONTINENT_LIST Custom, semicolon-separated continent list. Syntax is: CONTINENT_LIST=continent1;continent2;continent3 Default value: EU;NA;SA;AS;AF;OC
MULT1_CONT_LIST
MULT2_CONT_LIST
MULT3_CONT_LIST
Custom, semicolon-separated continent list. Syntax is: MULT1_CONT_LIST=continent1;continent2;continent3 Default value: EU;NA;SA;AS;AF;OC
OVERRIDE_INVALID_QSO_MESSAGE Suppress invalid QSO message for selected cases.
Syntax is OVERRIDE_INVALID_QSO_MESSAGE=IncaseRegexp1;AndRegexp2
Example: OVERRIDE_INVALID_QSO_MESSAGE=DEST->DXCC:^K$;DEST->RCVD:^$ will
not complain about empty RCVD field for US stations. (It will however not allow logging.)
Default value: None
MULT1_TYPE
MULT2_TYPE
MULT3_TYPE
Type of MULT. Can be DXCC, CQZONE, WPX, CUSTOM, HQ, NUM, FIELD, LETTER1, or FX. Default value: None
MULT1_FX
MULT2_FX
MULT3_FX
A C# expression used to create the actual value of MULT from the entered value.
The entered value is available in the object $FIELDVALUE.
For example MULT1_FX=$FIELDVALUE.Substring(0,$FIELDVALUE.IndexOf('/'))
will make the characters before the slash the actual multiplier.
MULT1_COUNT Counting method for MULT1. Can be PER_BAND, PER_PERIOD, PER_MODE, PER_BAND_MODE, PER_PERIOD_MODE, or ALL. Default value: None
MULT2_COUNT
MULT3_COUNT
Counting method for MULT2 and MULT3. Can be PER_BAND, PER_PERIOD, or ALL Default value: None
MULT1_ADD_DXCC
MULT2_ADD_DXCC
MULT3_ADD_DXCC
Function uncertain. Valid values: YES and NO. Default value: NO
MULT1_FIELD
MULT2_FIELD
MULT3_FIELD
Source of MULT. Valid values: RCVD, CALLSIGN, FROM_DXCC, FROM_WPX, RECINFO, RECINFO2, RECINFO3, NONE Default value: None
MULT1_DISPLAY
MULT2_DISPLAY
MULT3_DISPLAY
Text to show in MULT column. Syntax: MULT1_DISPLAY=Regexp;String. The Regexp can be omitted.
Example: MULT1_DISPLAY=DEST->DXCC:^K$|^KL$|^KH6$;S
Example: MULT1_DISPLAY=FN
Default value: None
MULT1_SHOWERROR
MULT2_SHOWERROR
MULT3_SHOWERROR
Highlight errors in MULT. Valid values: YES and NO. Default value: YES
MULT1_BAND_BONUS
MULT2_BAND_BONUS
MULT3_BAND_BONUS
Per band multiplier scaling factor. Syntax MULT1_BAND_BONUS=band;scaling.
Example: MULT1_BAND_BONUS=80;2 doubles the multiplier count for the 80m band.
MULT1_BONUS
MULT2_BONUS
MULT3_BONUS
General multiplier scaling factor. Syntax MULT1_BONUS=scaling.
Example: MULT1_BONUS=4 gives four multiplier points for every multiplier.
Default value: 1
MULT1_EXCEPTION
MULT2_EXCEPTION
MULT3_EXCEPTION
Exception from the general rule for MULT. Syntax: MULT1_EXCEPTION=boolean;multiplier definition.
The boolean function can either be a regular expression (as described above) or F() expression.
Example: MULT1_EXCEPTION=DEST->DXCC:^K$|^VE$;CUSTOM_MULT_LIST
will use the custom list to determine multipliers for US and Canadian stations.
Example: MULT1_EXCEPTION=FX(("CONFIG->CALLSIGN").Substring(0,3).Equals(("DEST->CALL").Substring(0,3)));NONE
will not count multipliers for stations that have the first three letters in their callsign equal to that of the own station's callsign.
This particular construct can be a replacement for OWN_MULT_VALID=NO in a national contest where the multiplier is the call area.
Valid values of the multiplier definition are: PFX_AREA, WPX, NONE, CUSTOM_MULT_LIST, REMOVE_DXCC, or LETTER1.
MULT1_MULTIPLIER
MULT2_MULTIPLIER
MULT3_MULTIPLIER
Multiplication factor for a selected value of MULT. Syntax multiplier;factor.
For instance MULT1_MULTIPLIER=AZ;4 means all "AZ" are worth four multipliers.
One MULT1_MULTIPLIER line is required for each value of MULT1 which has a multiplier.
MULT1_REPEAT
MULT2_REPEAT
MULT3_REPEAT
Specifies a list of values of MULT and the number of times they count as multipliers.
For instance MULT1_REPEAT=VD[3];PA[2] means the first three "VD" and the first
two "PA" count as multipliers. If only a multiplier without a bracketed number is listed, the number is one.
By default multipliers only count once
MULT1_CONT_LIST
MULT2_CONT_LIST
MULT3_CONT_LIST
List used when MULT is of type CONT. Default value: EU;NA;SA;AS;AF;OC
FIRST_PREV_RCVD Initial return value of macro $PREV_RCVD. Default value: "000"
FIRST_PREV_RECINFO Initial return value of macro $PREV_RECINFO. Default value: "000"
FIRST_PREV_RECINFO2 Initial return value of macro $PREV_RECINFO2. Default value: "000"
FIRST_PREV_RECINFO3 Initial return value of macro $PREV_RECINFO3. Default value: "000"
STATS_TYPE Type of statistics in Rate window. Valid values: STANDARD and WRTC. Default value: STANDARD
DISPLAY_TIME_ON_PER_MODE Display time on per mode in Rate window. Default value: NO
DISPLAY_LAST_MODE_CHANGE Display time of last mode change in Rate window. Default value: NO
BAND_MIN_LIMITS Bandwise minimum and maximum times. Only used by Bande Basse local Italian contest.
Syntax: BAND_MIN_LIMITS=band;maxminutes;minfromlastqsominutes.
MULTISINGLE_RULE10_ENABLED 10-minute rule for Multi-single operation enabled. Default value: YES
MULTISINGLE_RULE10_MINUTES Actual number of minutes for 10-minute rule for Multi-single operation. Default value: 10
MULTISINGLE_RULE10_CHECKMODE Checking principle for 10-minute rule. Default value: PER_BAND
MULTIOP_BANDCHANGECOUNTER_ENABLED Band change counter for multi operator operation enabled. Default value: YES
MULTIOP_BANDCHANGES_ALLOWED Number of band changes allowed in one hour in multi operator operation. Default value: 8
MULTIOP_BANDCHANGES_CHECKMODE Type of counting method for band changes in multi operator operation. Valid values: PER_BAND or PER_BAND_MODE Default value: PER_BAND
MULTIOP_BANDCHANGES_TYPE Type of band changes counted for band change rule in multi operator operation. R, RM, or ALL. (Run station, Run+Mult station, all stations) Default value: R
MULTIOP_BANDCHANGES_CBR_CATEGORIES Semicolon-separated list of Cabrillo operator categories subject to band change rule. Default value: MULTI-OP
MULTIOP_BANDCHANGES_CBR_TRANSMITTERS Semicolon-separated list of Cabrillo transmitter categories subject to band change rule. Default value: TWO
SLASH_MULTIPLE_QSOS Controls whether slashed ("/") multipliers are used in the contest. Default value: NO
SCORE Scoring principle.
Valid values: BY_BAND, BY_BAND_MODE, BY_PERIOD, BY_PERIOD_BAND, and BY_PERIOD_BAND_MODE
Default value: BY_BAND
SCORE_DISPLAY Displayed columns in Summary window. Default value: BAND;QSO;POINTS;MULT1
SCORE_TOTAL Principle for total score. Valid values: BY_BAND_GROUP and BY_MODE_GROUP. Default value: Empty
SCORE_TOTAL_FX Formula for calculating total score for a QSO.
Example: SCORE_TOTAL_FX=$FIELDVALUE.Points*$FIELDVALUE.Mult1+$FIELDVALUE.Mult3)*$FIELDVALUE.Mult2
No default value
SCORE_BAND_GROUP List of bands for PER_BAND_GROUP scoring.
Syntax: SCORE_BAND_GROUP=bandgroup1{band1,band2,band3};bandgroup2{band4,band5}
No default value
SCORE_MODE_GROUP List of modes for PER_MODE_GROUP scoring.
Syntax: SCORE_MODE_GROUP=modegroup1{mode1,mode2};modegroup2{mode3,mode4}
No default value
POINTS_FIELD_BAND_MODE Conditional point calculation.
Syntax: POINTS_FIELD_BAND_MODE=regexp1;regexp2;bandregexp;moderegexp;points
No default value
POINTS_CALC_F Formula for points calculation.
Syntax: POINTS_CALC_F=sourceregexp;pointsformula;bandregexp;calculationregexp
Example:POINTS_CALC_F=ALL;VALUE*5;^15$;QRB>=100 && QRB<=800 multiplies points
with 5 on 15m if QRB is between 100 and 800km.
All mathematical functions, plus the points number (VALUE) and distance (QRB) are available for expressions.
For some reason, integers sometimes need to be represented using the Floor() function, e.g. Floor(5).
No default value
DB_SCP_FROM_EXCHANGE or
DTB_SCP_FROM_RECINFO
Enable reverse look-up. Searches for all instances of either RCVD or RECINFO in first and second column of all data base files.
Search is triggered when pressing space and all entry fields are empty except RCVD or RECINFO.
Search hits are displayed in Check Partials window.
Default value: NO
WINDOWS_CML_ENABLED Enable custom multiplier window #1. Default value: NO
WINDOWS_CML2_ENABLED Enable custom multiplier window #2. Default value: NO
WINDOWS_CML3_ENABLED Enable custom multiplier window #3. Default value: NO
WINDOWS_CML_NAME Name of custom multiplier #1. No default value
WINDOWS_CML2_NAME Name of custom multiplier #2. No default value
WINDOWS_CML3_NAME Name of custom multiplier #3. No default value
WINDOWS_CML_LIST_FX
WINDOWS_CML2_LIST_FX
WINDOWS_CML3_LIST_FX
C# expression for the multipliers listed in custom multiplier window for MULT.
Syntax: WINDOWS_CML_LIST_FX=function.
Example: WINDOWS_CML_LIST_FX=GetList_PrefixArea(dxccList,"^VE$|^VK$|^JA$|^ZL$")
Example:
WINDOWS_CML_LIST_FX=GetList_CustomArray("A|C|CA|CC|CE|GI|GR|IB|J|L|LO||MU|NA|O|OU|P|SS|T|V|VI|Z","|")
No default value
WINDOWS_CML_DATA
WINDOWS_CML2_DATA
WINDOWS_CML3_DATA
Source of data for custom multiplier window 1, 2, and 3. Valid values: MULT1, MULT2, MULT3, QSODIFF, QSODIFF_SP, and QSODIFF_CQ. No default value
WINDOWS_CML_SHOW_GROUP
WINDOWS_CML2_SHOW_GROUP
WINDOWS_CML3_SHOW_GROUP
Controls if customer multiplier window 1, 3, and 3 show the multipliers grouped, is such are defined. Valid values: YES and NO. Default value: NO
WINDOWS_CML_RESIZABLE
WINDOWS_CML2_RESIZABLE
WINDOWS_CML3_RESIZABLE
Controls if custom multiplier windows are resizable. Default value: NO
WINDOWS_CML_LABELS_IN_ROW
WINDOWS_CML2_LABELS_IN_ROW
WINDOWS_CML3_LABELS_IN_ROW
Controls number of MULT labels in each row of its custom multiplier window.
Valid values: -1 and positive integers. -1 means DXLog default.
Default value: -1
WINDOWS_CML_ALL_LABELS_IN_ROW
WINDOWS_CML2_ALL_LABELS_IN_ROW
WINDOWS_CML3_ALL_LABELS_IN_ROW
Controls the number of MULT labels in all each row of its custom multiplier window when there is no fixed list of
allowed multipliers and the window therefore grows gradually during the contest, such as the HQ multiplier in IARU HFC.
Valid values: -1 and positive integers. -1 means DXLog default.
Default value: -1
WINDOWS_CML_HIDDEN_CONT
WINDOWS_CML2_HIDDEN_CONT
WINDOWS_CML3_HIDDEN_CONT
Hides a custom multiplier window for stations from selected continents. Currently not used in any contest. Default value: None
WINDOWS_CML_HIDDEN_DXCC
WINDOWS_CML2_HIDDEN_DXCC
WINDOWS_CML3_HIDDEN_DXCC
Hides a custom multiplier window for stations from selected DXCC.
Syntax: WINDOWS_CML_HIDDEN_DXCC=list
Example: WINDOWS_CML_HIDDEN_DXCC=*+G;GI;GW;GM;GJ;GU;GD hides the MULT1 window for UK stations.
Example: WINDOWS_CML_HIDDEN_DXCC=*-SM;LA;OZ;OH shows the MULT1 window only for Scandinavian stations.
No default value
WINDOWS_WKD_DXCC_ENABLED Enables worked DXCC window. Valid values: YES and NO. Default value: NO
WINDOWS_WKD_DXCC_HIDDEN_CONT Hides worked DXCC window for stations from selected continent.
Example: WINDOWS_WKD_DXCC_HIDDEN_CONT=*-AS shows only the worked DXCC window for Asian stations.
No default value
WINDOWS_WKD_DXCC_HIDDEN_DXCC Hides worked DXCC window for stations from selected DXCC. C.f. WINDOWS_CML_HIDDEN_DXCC above for syntax. No default value
WINDOWS_WKD_DXCC_SHOW_ONLY_CONT Show only entities from the listed continents in the worked DXCC window.
Example: WINDOWS_WKD_DXCC_SHOW_ONLY_CONT=NA;SA shows only NA and SA entities in the worked DXCC window.
No default value
WINDOWS_WKD_DXCC_CONT_FILTER Defines a subset of DXCC entities from a certain continent to include in the worked DXCC window.
Example: WINDOWS_WKD_DXCC_CONT_FILTER=SA:9Y;P4;PJ2;PJ4 will only include 9Y, P4 and PJ2 from South America.
No default value
WINDOWS_WKD_DXCC_HIDE_DXCC Hides a list of DXCC entities from the worked DXCC window.
Example: WINDOWS_WKD_DXCC_HIDE_DXCC=K;VE hides US and Canada from the worked DXCC window.
No default value
WINDOWS_WKD_GRID_ENABLED Enables worked grids window. Valid values: YES and NO. Default value: NO
WINDOWS_WKD_PFX_ENABLED Enables worked prefixes window. Valid values: YES and NO. Default value: NO
WINDOWS_WKD_PFX_HIDDEN_CONT Hides worked prefixes window for stations from selected continent. C.f. WINDOWS_WKD_DXCC_HIDDEN_CONT above for syntax. Default is to hide nothing
WINDOWS_WKD_PFX_HIDDEN_DXCC Hides worked prefixes window for stations from selected DXCC. C.f. WINDOWS_CML_HIDDEN_DXCC above for syntax. Default is to hide nothing
WINDOWS_WKD_PFX_DATA Source of worked prefixes data. Valid values: MULT1, MULT2, and MULT3. No default value
WINDOWS_ON4KST_ENABLED Enables ON4KST messaging window Default value: No
CABRILLO_EXPORT_TYPE Controls structure of Cabrillo export. Valid values: PER_MODE and ALL. Default value: ALL
LIVESCORE_CONTEST_NAME Contest name used for live score reporting. Default value: CABRILLO_CONTEST_NAME.
LIVESCORE_OPERATOR List of types of operation used for live score reporting. List must have the same number of items as mode categories. Default value: CABRILLO_OPERATOR
LIVESCORE_POWER List of output power classes used for live score reporting. List must have the same number of items as mode categories. Default value: CABRILLO_POWER
LIVESCORE_TRANSMITTER List of number of transmitters categories used for live score reporting. List must have the same number of items as mode categories. Default value: CABRILLO_TRANSMITTER
LIVESCORE_ASSISTED List of assistance categories used for live score reporting. List must have the same number of items as mode categories. Default value: CABRILLO_ASSISTED
LIVESCORE_MODE List of modes used for live score reporting. List must have the same number of items as mode categories. Default value: CABRILLO_MODE
LIVESCORE_MULT List of multiplier "names" in numerical order used for live score reporting. Must have the same number of items as contest multipliers. By default DXLog uses "country", "zone", "prefix", and "state".
QTC_ENABLED Enables QTC mechanics. Default value: NO
QTC_SEND_ENABLED Enables QTC sending. Default value: !SOURCE->CONT:^EU$
QTC_RECV_ENABLED Enables QTC receiving. Default value: SOURCE->CONT:^EU$
QTC_SEND_RGX Regular expression controlling the transmission of QTC. Default value: DEST->CONT:^EU$
QTC_RECV_RGX Regular expression controlling the reception of QTC. Default value: !DEST->CONT:^EU$