Revised augmented logs for CQ WW SSB from 2005 to 2016

I recently added another column to the flags on each line of the CQ WW SSB augmented logs for 2005 to 2016 (the MD5 hash of the file is 3ba5bc3d157cb7b7d1974832b82f81e5). However, K0KR reminded me that some logs contain frequencies that merely indicate the band, not the actual frequency of the QSO. In such logs, it is not possible to determine whether a logged QSO was part of a run. Therefore I have changed the values and meaning of the new column (column #11) as described below.

The additions to the standard CQ WW Cabrillo QSO line are now (changes in bold):

1. The letter "A" or "U" indicating "assisted" or "unassisted"
2. A four-digit number representing the time if the contact in minutes measured from the start of the contest. (I realise that this can be calculated from the other information on the line, but it saves a lot of time to have the number readily available in the file without having to calculate it each time.)
3. Band
4. A set of eleven flags, each -- apart from column k -- encoded as T/F: 

• a. QSO is confirmed by a log from the second party 
• b. QSO is a reverse bust (i.e., the second party appears to have bust the call of the first party) 
• c. QSO is an ordinary bust (i.e., the first party appears to have bust the call of the second party) 
• d. the call of the second party is unique 
• e. QSO appears to be a NIL 
• f. QSO is with a station that did not send in a log, but who did make 20 or more QSOs in the contest 
• g. QSO appears to be a country mult 
• h. QSO appears to be a zone mult 
• i. QSO is a zone bust (i.e., the received zone appears to be a bust)
• j. QSO is a reverse zone bust (i.e. the second party appears to have bust the zone of the first party)
• k. This entry has three possible values rather than just T/F:
• T: QSO appears to be made during a run by the first party
• F: QSO appears not to be made during a run by the first party
• U: the run status is unknown because insufficient frequency information is available in the first party's log 

Note that the encoding of some of the flags requires subjective decisions to be made as to whether the flag should be true or false; consequently, and because CQ has yet to understand the importance of making their scoring code public, the value of a flag for a specific QSO line in some circumstances might not match the value that CQ would assign. (Also, CQ has more data available in the form of check logs, which are not made public.)

Note also that I made no attempt to deduce the run status of a QSO in the second party's log (if such exists), regardless of the status in the first party's log. This allows one cleanly to perform correct statistical analyses anent the number of QSOs made by running stations merely by excluding QSOs marked with a U in column k.