At each round Vega runs the executable engine with the following command:
$>
engine_name
tournament_path
file_name.trfx
where tournament_path is the path of the tournament folder, and file_name.trfx is the file
automatically generated containing the tournament data. In this way the engine is correctly
addressed where the important tournament files are with appropriate parameters.
NOTE: It is recommended that the tournament_path does not contains blank space or unusual
characters to prevent the engine to work correctly.
NOTE: It is responsibility of the extern engine to retrieve all the relevant
tournament
data from the trfx file saved by Vega in the tournament folder. The engine must save all its
output in the tournament folder.
Vega expects from the engine a file that at round N should be named as engine.man containing
the pairing at round N in the following format: a first row with the number of the pairs, and for each
successive row, the IDs of the player of each pair. This is a typical *.man file containing 5 pairs:
5
5 2
17 10
16 13
8 11
9 3
(the BYE has ID=0). If this file exists Vega will load it and continues with the insertion of results
and making all the ranking lists.
The file_name.trfx is used by Vega to pass sensible data to the external pairing engine. This
file is used, for example, by JaVaFo engine of Roberto Ricca.
The extension trfx stands for eXtended Tournament Report Format. The file is a slight modification
of the one used by FIDE for rating report as specified by its creator Mr. Christian Krause. The
following specification comes from the FIDE web site
77