Band and point value are separated by at least 2 spaces.
File format example:
144  1
432  2
1.2  5

Non integer values can also be used:
50  .1
144 .5
222 1
432 1

Independent summaries: Several summaries can be called using the Table1 setup. These headings are put at the bottom of the list, and don`t require an output column number.
Created-By
N-QSO totals
State QSO Party
Mode Summary
Sponsor Specific Table outputs
The [Sort Table by QTH and Power Category] in the right part of Table1 setup was for specific sponsors, and probably will not work for you.

Using the heading "Category-Mode" without the output column ID is another mode summary.

The Table1 summary file is written using the Summary menu - or - using the Write... menu while in the Table1 Preferences setup.

Only specific heading data is available from the `results` files - selected from combo-box.
Ex: The ARRL/DX data comes from the ARRL-SECTION: and LOCATION: tags in Cabrillo.

Select the data and the Tab column for each. In the example: The callsign would be in <Tab> column 7 of the output file and QSOs would be in column 18.

Typical output is like this:


If you want the summary data in close spaced columns, set the columns you want and ignore the heading overlap.
However, since the heading row is not space-delimited, export to Excel will not be correct - not space-delimited.


Note:
The Table1 Files write function uses the CATEGORY: and other data in the results files {call.txt} for lookup. Before batch scoring, you should edit the Cabrillo CATEGORY: field of the offending logs so the sorting routine will find a match - according to what you set up in the Table1 Files setup screen. Printing the list of Cabrillo logs evaluated will help locate logs that need to be edited or check off the logs that do not. Use Summary, Write Cabrillo files list.



If the Table is blank when you start a new contest profile, select the Fill with defaults menu to show you the format, then edit the table to your liking.

Or at any time, use the Fill State QSO Party menu to setup the Table1 output with the most common QSO Party summary information. You can always re-load your Ini file to go back to the original setup.

Note:
When the `County` heading is used, the software reads both in-state and out-of-state Ini files to determine the sent and received exchange columns. If you make a change to the setup, re-save the Ini file(s) before writing the summary.


If you intend to keep the Table1 changes, re-save the contest Ini file.

Note:
If your contest uses 2 Ini files (State QSO Parties and Home/DX Ini files) and the expected Table1 summary is not written, check the 2 Table1 setups. Different setups may have been saved to the 2 Ini files.

This selectable options setup is used to output the contest summary in 6 sections - sorted by HIGH, LOW and QRP categories.

Used in conjunction with the Home Country/Continent and DX Countries 2-Ini files setup, the six output sections are HIGH, LOW and QRP power for each of the 2 QTHs. This option is hard coded except for some text that you want in the header of each section - as below.


From the above setup, the 6 sections are labled as:
Europe Stations - High Power
Europe Stations - Low Power
Europe Stations - QRP <=5W
DX Stations - High Power
DX Stations - Low Power
DX Stations - QRP <=5W

Select sort by Single-Band(MHz) or Single-Band(Meters) to write the single-band field to the `results` file.


Note:
In contests with more categories than can be supported by CabEval - SOAB HIGH, SOAB LOW, 80M HIGH, 80M LOW, 80M QRP etc. you must manually sort the summary to your liking - see Excel export below.

Sorting the score results into HIGH, LOW and QRP categories is done using data in the CATEGORY: field of the Cabrillo log. The text HIGH, LOW or QRP must be in the category field. ex: CATEGORY: SINGLE-OP ALL HIGH

If the category does not have a power level (ex: CATEGORY: SOAB or Single-Op), unselect the {Sort by QTH and Power Category} check-box and use a setup like this:


for an output like this:


Cabrillo v3.0 uses the Category-Operator tag, which can be used to capture the category as well.

If the logs are a mixture of v2.0 and v3.0, try using both the Category and Category-Operator headings.

Or use the new heading Category-v3 that will capture the following v3.0 tags in most cases:
CATEGORY-OPERATOR: SINGLE-OP
CATEGORY-POWER: LOW
CATEGORY-MODE: CW

Another new heading State QSO Party runs a totally different summary. The State QSO Party heading is put at the bottom of the list and does not require a column #, since the heading calls the special summary routine.

If the State QSO Party heading is in the list, only this summary will be written. This makes it easy to go back to your initial summary output without changing the entire list. If you like the new summary, re-save the Ini file.
Output file = [State-QSO-Party-Summary.sum]
Mode Summary is also an independent summary that is added at the bottom of the list without a column #. You can output your normal Table1 summary that is saved to the contest Ini file, then simply add `Mode Summary` at the bottom to write just the mode summary. Remove it when done.

Created-By heading:
Add this heading to the bottom of the table list, without a column #. It outputs the list of popular logging programs used in the contest being scored. The output file is {Logging-Programs.sum}.
The Created-By data comes from the results text files.

Logging Program heading:
Adding this heading with a column # outputs the logging program versions, by Callsign.{Target=NQSOs}

N-QSO totals heading:
Add this heading at the bottom of the table list, without a column #. It outputs the summary of N-QSO totals for each log.
Of course, N-QSO = N must be selected in the Sponsor Setup before scoring logs.
See N-QSO rule: in the Sponsor Setup.
Data comes from the results text files. Output file is [N-QSO-totals.sum].

Op Time heading:
Selecting the `Op Time` heading will output the total hours operated. UTC times between QSOs of <30 minutes are considered ON-TIMEs, and are counted in the total.
Note: If the Op time displayed is a negative value, the log file could be in reverse date/time order - or a date/time sequence is out of order. Manually edited logs (including QSOs added out of order) may produce negative values and possibly a program error. Use the Modify Logs, Log Tools, Log Date/Time sort menus to sort the log in date/time order.

Sponsors can output more than 1 Table1 summary easily by saving (and re-loading) different Ini files. Using "Table1-A" text in the filename for example will identify the Ini file as a special setup to write various Table1 summaries. Be sure to re-load the actual scoring Ini file before scoring logs.

Sponsor specific headings:

Sponsor specific Table1 outputs are like the above State QSO Party summary and do not require a column #. It is easiest to select the heading as the last one in the setup. If one of these sponsor headings is selected, then only that table summary is written. Some sponsors want their output to be similar to their web page summaries, for ease of use.
Output file = [ARCI-QRP-Summary.sum]


Another sponsor specific Table1 summary output.
Output file = [SCR-Summary.sum]
_________________________


When VHF/UHF Rover logs are scored using the {ARRL method}, the number of multipliers displayed in the Table1 output will be higher by the number of activated grids, as shown in this Sprint summary output. In the example, K1DS/R worked 13 grids and activated 2 grids while roving.

CabEval can also score VHF/UHF Rover logs in the {Classic Rover} method, where the multiplier total is only the total mults worked.

WPX multiplier summary:
This summary selection writes the {WPX_Multiplier.sum} file, which is the total number of unique WPX prefixes for SA and NA stations.

Show score for one band - SOSB Category:

Note: Contesters do not always use the correct Category, so if the Category is ... 80M ... and 95% of the log is 20M for example, obviously the 80M SOSB score will be very low. Therefore the use of the {Calculate SOSB score} function needs some thought - or maybe even an e-mail to the contester.

CWJF Manchester Mineira contest example.

Select the {Calculate SOSB scores} check box to display the single-band score declared in the CATEGORY: or CATEGORY-BAND: field. The categories would be SOSB 80m, SOSB 15m etc. The actual lookup text is in the format designated in the contest rules, and is stored in the {SOSB_Categories.dat} look-up file. My generic category file has 3 formats for each band - so the lookup will work for most Cabrillo category formats: SOSB 15M, Single-Op 15M and Single Op 15M as examples. Edit this file to suit your contest.

Since the exact wording of Categories can be different, it is easiest to just put bands (in meters) in the lookup file. For example: the word "40M" will be found in any 40M mode category.
example:
80M
40M
20M
etc.

The software uses the results files (callsign.txt) for scoring data and loops thru all the categories in the {SOSB_Categories.dat} file and writes the single-band score based on the CATEGORY: or CATEGORY-BAND: tag of the log.

First, check for logs that are multi-band, but the category is single-band:
1. Use the Write Cabrillo Files list menu to display the categories - some categories will be missing, some may not follow the convention outlined in the rules.
2. Use the Check Categories, Check SOSB Categories menu to check the logs that have the wrong category.

To see the new SOSB scores, first write the normal score summary. Do `Save As` and rename it with "-initial" in the filename, for example. Select the {Calculate SOSB score} function and write the summary again. Compare the log scores. If you use EditPad, you can have both files open in the same editor, in a tabbed interface.

This option can be used with the {Sort by QTH and Power} option explained above. The summary display below is for SA Station, SOSB 15m, QRP.


The single-band score is taken from the results text file of a previously scored log. This single-band score can only be calculated in the Table1 output. In this example, the 15m score 14 * 4 = 56.


Hint: Use the Write Cabrillo Files list menu to see the different category formats of the submitted logs, as some may not follow the convention outlined in the rules.


Note: Since the log may be used for cross-checking and CabEval needs the whole log scored, the non-15m QSOs cannot be discarded prior to log scoring.

Show score for one mode - SO Mode Category:

Select the {Calculate SO Mode scores} check box to display the single-mode score declared in the CATEGORY: or CATEGORY-MODE: fields. As with the SOSB function, the Single Mode score calculation function uses a lookup file - {SOMode_Categories.dat}. Edit this file to suit your contest.

Since contesters do not always use the categories in the rules, use just the modes in the lookup function - CW, SSB, PSK. Put your contest modes in the {SOMode_Categories.dat} file, one mode to a line.
example:
CW
SSB

Notes:
The software uses the results files (callsign.txt) for scoring data. Since the QSO points are read from the results files, the [QSO points are:] setup must be set to [by Mode] or [by Continent] for the mode calculation to work. The points per QSO are not written to the results files when [QSO points are:] [All the same] is used.

In the {Include} menu, you must select {Multiplier QSOs in Eval text file} and {QSO points in Eval file} before doing the actual log scoring, otherwise there won`t be any data in the results files to count Mults and Q-points. Verify that these menu items are check-marked.

The function loops thru the categories in the {SOMode_Categories.dat} file and writes the single-mode score based on the mode in the CATEGORY: or CATEGORY-MODE: tag of the log being summarized.

First, check for logs that are mixed-mode, but the category is single-mode:
1. Use the Write Cabrillo Files list menu to display the categories - some categories will be missing, some may not follow the convention outlined in the rules.
2. Use the Check Categories, Check SO Mode Categories menu to check the logs that have the wrong category.

To see the new SO mode scores, first write a normal score summary. Do `Save As` and rename it with "-initial" in the filename, for example. Select the {Calculate SO Mode scores} function and write the summary again. Compare the log scores. If you use EditPad, you can have both files open in the same editor, in a tabbed interface.

The results of the re-calculation based on Single Mode should be checked. The CATEGORY: mode that the contester used may be incorrect, resulting in a score for 5 SSB QSOs, when 95% of the log is CW.

Excel export:
If the contest results are published with more categories than can be sorted by CabEval, then you may want to sort the summary file in Excel. In the Table1 setup, select Country or Continent (or both) to write those fields to the {ScoreSummaryFile.sum} file. The export function loads space de-limited text files into an Excel worksheet, so other tabular summaries (or any ASCII file) can also be exported - not just the Table1 summary.

Then select the Summary Export to Excel menu.
  
     Sort by Country or Continent                                       or by both.

In the Table1 setup when you select Country, you can select Country-Text to have the Country name (Italy, Poland etc.) included in the output file.


Hint: If you use the Category field, put it last in the setup, since the category text can be long, which takes up more than one cell when exported to Excel.

The Excel export is a space delimited function - so 2 word country names will be separated into 2 columns - F & G in this example.
 
Rows F and G can be concatenated (combined) - column H.
Then the references from F and G are removed to use just column H.

To combine columns F and G starting on row 2 for example: click row 2 of column H. Enter the formula  =F2&" "&G2  which will add F and G as text with a space between them. Drag the formula from the first row to the last row to be combined. To remove the reference columns F and G from the speadsheet, select all the items in column H and do right-mouse `Copy`. Click row 2 in column H and do right-mouse `Paste Special, Values`. Delete columns F and G.

The filename of the .sum file selected for export will be used as the filename for the Excel output file - with the extension .xls.The Excel file will be written to the {Results} folder - where the {ScoreSummaryFile.sum} file resides.

Excel auto open:
To have the file opened in Excel after it is written - like text files that open in your editor - use the Options Ini Setup to set the path to Excel.exe. If not, you can always open the file in Explorer.


Table2 Files setup

---

In the Summary menu, a second preferred table setup is available - used to write sorted score text files. Select the Preferred Table2 Table2 Preferences menus.  Or - use the Table1 setup to make a table that can be exported to Excel for more sort flexability.

The text files can be written using the Summary menu - or - using the Write... menu while in the Table2 Preferences setup.

See file write setup for contests not using 2-Ini files below.

Sorting can be setup for one of two ways - strictly `by Category only` for single location contests or used in conjunction with the Home and DX stations (or Home and Away state) 2-Ini files setup in the Sponsor`s setup form. There are 7 different output text files that can be written. If some of the 7 files are not required, the fields are left blank.

If the Table is blank when you start a new contest profile, select the Fill Table with defaults menu to show you the format, then edit the table to your liking. Re-save the contest Ini file(s) when you make changes to this setup.

Note:
The Table2 Files write function uses the CATEGORY: in the results files {call.txt} for lookup. The CATEGORY: field in the Cabrillo logs must be checked (and possibly edited) for the files sort function to work properly. You can be assured that not all submitted logs will have the correct CATEGORY: information.
Before batch scoring, you should edit the Cabrillo CATEGORY: field of the offending logs so the sorting routine will find a match - according to what you set up in the Table2 Files setup screen. Printing the list of Cabrillo logs evaluated will help locate logs that need to be edited or check off the logs that do not - Do Summary Write Cabrillo files list. Partial output shown.

These 5 logs have different categories (with/without dash), but a match is found and the 5 scores were written to text files. The 2 main categories in the Table2 Files setup were:
SINGLE-OP ALL LOW and SINGLE-OP ALL HIGH.

Matches are found in the above example due to the expanded lookup matching - which to a certain extent disregards the exact placement of these categories using the {dash -} in the text.
SOAB-HIGH = SOAB HIGH = SINGLE-OP ALL HIGH = SINGLE OP ALL HIGH
SOAB-LOW = SOAB LOW = SINGLE-OP ALL LOW = SINGLE OP ALL LOW etc.

This `by Category only` sample is for the Spring Microwave Sprint and the selector check-box is checked.

This example is for the UK-DX RTTY Contest - the check-box is not selected - the default setting. The `location` sorting comes from the 2-Ini files setup - UK and non-UK stations.

In this setup, you enter the CATEGORY: information for each group. ie: SOAB-HP in the first position. All logs that are UK stations and SOAB high power are sorted and the score summary for each is written to the { UK-SOAB-HP.txt } file. These output files are written to the application startup folder, not to the `results` folder if one is selected - because these sorted output files would conflict with summary functions using the *.txt results files.


The number of log results and the number of files written are displayed in a dialog message at the end of the write function. If the number of logs does not agree with your total, check the CATEGORY: data in the `results` and Cabrillo files. Printing the list of Cabrillo logs evaluated will help locate the missing log(s) - Do Summary Write Cabrillo files list.

The data for the output files comes from the `results` text files { logfilename.txt }.
CALLSIGN: G4XYZ
Contest Ini file: UKDX_RTTY_UK.ini
CATEGORY: SOAB-HP  <---
Totals   18      47       19
Actual Score: 893  *********

Contesters should follow the rules as far as their CATEGORY: in the Cabrillo logs, but do not always do so. Also, the sponsor`s contest rules should dictate what the categories are if they want to use the Table Files function.

Note:
Write the Cabrillo files list first to see what the majority of categories are. This will reduce the number of CATEGORY: edits.

Note:
If you finished batch scoring lots of logs and the category fields need editing, you must edit the {call.txt} results files, not the original Cabrillo files. You can edit the Cabrillo logs, but you must re-do the batch run to update the category field in the results files.

Setup for contests not using 2 Ini files for `Home` and `DX` for scoring.

In this 10-10 Open Season 10m PSK Contest example, the 2 catgories Low and QRP are sorted based on the ARRL-Section: field in the Cabrillo. `DX` and `Home/non-DX` stations.


UTC Date and Time

---

The UTC Start Date and UTC Start Time fields are use to verify the first QSO in the log.

Sponsors:
If you do not care whether the log times are valid, or whether times are local time or UTC and want to turn off this function, select this option at the top of the Options Ini Setup.

The year of the first QSO is also checked to verify that the log file is a current file for the contest being checked. A station may submit an old Cabrillo file - ie: the wrong file was sent to the contest sponsor.

No UTC End Date or End Time fields are provided. CabEval does not check the date and times of QSOs to be within a specified range.

UTC delta more than 5 minutes:
There should not be a penalty for slightly inaccurate PC clocks. By default, the CC software uses a 5-minute rule for UTC time difference between QSOs - more than 5 minutes, the QSO will be NIL. The default UTC delta can be changed in the optional Ini setup, accessed in the main screen using the Ini Options menu or using File, Sponsor Setup, Ini options menus.


Where in the Cabrillo

---

This field identifies what column of the QSO line in the Cabrillo file that is used for the search/look-up - and the length of the look-up string in the file.

Some log checker software may use <Space> parsing of the space delimited data, CabEval does not - software was written in 2000 when contests used column ID templates at http://wwrof.org/cabrillo/. A simple solution is included in the SW - run all submitted logs in a re-formatting function that uses the space delimited format to put the Cabrillo data in the proper columns used by the software.


The above setup is for the {DXCC} look-up. The callsign from column 56 of the Cabrillo file is used to look-up the DXCC prefix and the string is 12 characters long. The software does the trim( ) function to remove the blank spaces after a callsign.

Note:
Even if the DXCC mult look-up function is not used, you need to identify the column and width of the received callsign in the Cabrillo file. The evaluator uses this data when determining the station`s country origin - plus the {by Continent} QSO points, {by Callsign} QSO points, {by callsign} WPX multipliers - etc.


Below the DXCC field are the settings for the {Other} look-up. The multiplier in column 74 of the Cabrillo file is used to look-up the state, section, prov, club number, etc and the length of the string is 4 characters. The software does the trim( ) function to remove the blank spaces.


In contests where multipliers are counted, but a multiplier look-up file is not used, the filename {none.dat} is used. For example: different 4-digit Grid Squares are used as one type of multiplier in the `Low Power Sprint` contest. You need to define the column and width in {Where in Cabrillo} for the multiplier data to be evaluated. The 4-digit locators in this example are at column 76 and width 4 characters in the Cabrillo file.

--- End of file ---