Difference between revisions of "Files"
|Line 159:||Line 159:|
Files are named
Files are named .edi, f.e. 06OK2M.edi. Format is very similar as txt files, the only one difference is missing section [TUCNAK extension].
Revision as of 15:07, 11 September 2012
Remark: Character ~ (tilde) is short cut of user home directory (bash# echo $HOME). Under Windows it poins to user's AppData folder.
Files which are described below are saved in plain text format. Is possible to edit these files but it is necessary to keep format of files. In other case Tucnak shouldn't work properly.
Note files in /usr/share/tucnak2/ are only examples and are not read by tucnak. These files are default values hard-wired in tucnak binary. You can copy into ~/tucnak and modify them. Tucnak will use files in ~/tucnak instead of compiled-in data.
- 1 Binaries
- 2 Configuration
- 3 Call database
- 4 DXC files & others
- 5 Contest files
- 6 Output files
- 7 System files
Is one binary file. If Tucnak is install from source code it's installed to /usr/local/bin. If Tucnak is install from package it's installed to /usr/bin mostly. On Debian it's /usr/bin/tucnak2 and command tucnak2 is found via /etc/alternatives.
Suided binary allows to access to /dev/console for PC speaker control (Linux only)
Configuration file of Tucnak program. When it don't found configuration file it reads from internal hardcoded default.
This file has the same structure as tucnakrc file. Is determine to set specific local options, when you synchronize tucnakrc between more computers. Tucnak only reads this file after loading tucnakrc. It is necessary to create and maintain it manually.
Use is obsolete. I think tucnakrc synchronize brings many problems. It is better to have separate tucnakrc and maintain they by program.
File with apair callsign-locator. Each callsign has saved maximally two locators. Format is similar to Taclog's taclog.c_w but not same when one call has two wwls. Format is:
CALL WWL YYYYMMDD QRV
DR5A JO30EM 20071006 CEGHK
Second locator is saved as next line.
Here you can save first names of operators and say them 'Hello John' :-). Tucnak updates this database on demand from DL8EBW database. Of course you can maintain it manually.
Template for qrv. It is copied to contest directory when you create new contest. Note: not when you created contest from network. In this case qrv database is transferred over network.
User definable master.db database for shortwaves. If not present, tucnak uses internal hardcoded (probalby not actual) database.
Like tucnakcw contains database of callsigns, their optional exchanges (EXC, OE) and datestamp. XXX is name of EXC for example OKRES (Czech districts) but in lovercase (~/tucnak/tucnakexcokres). Format is:
CALL EXC YYYYMMDD
OK2BKP GKR 20081006
Second locator is saved as next line.
List of all available optional exchanges if verified EXC's are used. XXX is name of EXC for example OKRES (Czech districts) but in lovercase (~/tucnak/tucnakvexcokres). Format is free, Tucnak reads all lines from file and uses all words sepparated by spaces or tabs. f.e.
APA APB APC APD APE APF APG APH API APJ BBN BBE BKD BKO BKH BME BMB BNY BPZ BPV BPB BRA CBU CCK CJH CPE CPI CPR CST CTA
DXC files & others
All these files are optional. Tucnak is reading these when are existing, in other case uses own hardcoded defaults.
File with information about DXCC countries. Each country has saved information about possible large squares and centre of activity in the country. Tucnak doesn't write to this file. Format of file is:
# 1th row - The official prefix of the DXCC # 2nd row - The list of WWL in the DXCC (separated by a gap). # The first WWL is the most effective one or midlands # or Capital City of DXCC. # 3rd row - The most effective WWL from JN69UO # There is a free row between DXCC's # OK JN79 JO70 JO60 JO80 JO90 JN69 JN89 JN99 JN68 JN78 JN88 JN98 JO71 JN89JM JO80IA
Follows up information to tucnakdw. Tucnak doesn't write to this file. You can download new version from http://www.country-files.com/cty/index.htm and place it into ~/tucnak.
This file contains information about contest as kind of pointing, etc. Tucnak doesn't write to this file. Items are described in Contest options.
This file is maintained by Guy, DL8EBW and contains informations about many stations qrv on VHF bands. Copy file like VHF250.DBF to ~/tucnak/vhf.dbf, open contest and choose Menu->Import DL8EBW Database. Tucnak reads:
- Locators of unknown stations to tucnakcw (only unknown because database may contain older locators than tucnakcw, timestamp cannot be processed by computer)
- Names of calls if they are longer than 2 characters.
If the file is not found, tucnak try to read /usr/share/tucnak2/vhf.dbf (depends on DESTDIR argument of configure)
Each contest is saved to differed directory. Name of directories is created from date of contest e.g. ~/tucnak/2003083.1. It is possible to have many contest in one day or one contest on one computer under one user (thought telnet, ssh) with many running Tucnaks. Each contest with the same date has different number behind point.
Files in ~/tucnak/<date>:
Named <letter>.txt e.g. c.txt, e.txt. This files are main files for individual bands. Files use information about station, QTH, points of both finished and unfinished contacts. Format is compatible with EDI format and should be accepted by contest comitee. Files has DOS end of line (`\r\n') for compatibility.
Are <letter>.swp eg. c.swp, e.swp. Here is saved all typed text from input line ended by Enter key. You are able to reconstruct all contest exchange manually from this file.
Contains information displayed in start of contest as date of contest, callsign and name of contest.
Content of log window.
Information about received skeds
Specify hosts and bands on which tucnak does spy
Content of talk window. That's good idea to read after contest :-)
Contains highlighted calls from DX-Cluster and OK4KST chat
QRV file format was changed since 2.38. Newer version should import old format but writes only new format.
File is imported from external script, you can prepare your own criteria. Some items are updated when you select line in shell window running the KST chat.
Leading semicolon tells file is in new format. Follow call and locator. GHK are bands on which this call is QRV. Next item tells number of contact we mate in last period. Negative number means we make this call never but other stations do. @QRV is remark for additional informations. @QRV means info comes from qrv script. Last one is timestamp when call was last caught on KST.
old qrv until 2.38
Contains list of stations that are QRV in contest. Functionality is described here. Format is:
CALL WWL CALL WWL BANDS DESCRPTION
OK2M JN69UN OK2M JN69UN CEGHK Skeds via KST
Holds informations about files displayed in chart window.
Zero means record is for first chart window. Follows file name (TXT or EDI).
Commonly files are saved to contest directory.
Filenames have format YYYYMMDD_CALL.adif. Exported are all qsos into one file.
Filenames have format YYYYMMDD_CALL.cbr. Exported are all qsos into one file.
Files are named CategoryCall.edi, f.e. 06OK2M.edi. Format is very similar as txt files, the only one difference is missing section [TUCNAK extension].
By pressing F1 you can make screenshot of Tucnak window. ALT+F1 takes snapshot only of top dialog/window. Filenames are in format snapN.png where N is number 0, 1, 2, ... Screenshot are saved to contest directory or in ~/tucnak/ when no contest is opened.
Contacts from all bands are saved in YYYYMMDD_CALL.html. Also creates map and chart for all bands with at least one QSO.
Report is format used in small OK contest like OK VHF activity contest. It summarizes callsign, locators, QSO count, QSO points, multipliers and total score. It is in Czech language only.
Creates HTML of similar format as title page of old paper log.
Creates post-contest report in MediaWiki format. Usable as skeleton for contest story web page. Also creates map and chart for all bands with at least one QSO.