Bridge Suite uses two files: INxxx.txt for the list of the boards to play as input file, and OUTxxx.txt where their results and bidding sequences are added, as output file
The file name, in addition to the root IN and OUT is greated by the concatenation of the Pair, Table or Board set number. In front to the Table and Board set number a T or B, respectively, is added.
E.g. the full file names are
IN_1.txt IN_2.txt IN_101.txt IN_102.txt
OUT_1.txt OUT_2.txt OUT_101.txt OUT_102.txt
for Pair 1, 2, 101 and 102, respectively
IN_T1.txt IN_T2.txt IN_B1.txt, IN_B4.txt, and the same for files OUT
for Tables 1 and 2 and Board set 1,2,3 and 4,5,6 respectively.
For Board number the number of the first board of the set per turn is used. In the above example we have 3 boards per turn.
Where are the files stored
If, as by default, the Cloud Dropbox is used, the files are in the folder, set in Preferences, starting from Dropbox root. Their content is automatically synchronized between the tournament PC and all tablets.
If instead the SDCARD preference is selected, the file folder is in the SDCARD memory root.
If Dropbox is not used, it is a task of tournament manager saving and reading the files to and from the tablet SDCARD..
CSV format is used, i.e. strings separated by commas and new lines.
IN file record fields are
table, board, NS pair, EW pair, dealer, NS vulnerable , EW vulnerabile
for instance, the IN file on the tablet/Smartphone used by pair 2 (IN_2.txt) is:
N.B.: The above example is from an Howell tournament where pair 2 plays both as NE and as EW, but in IN_2 file there are only the hands where they play NS, otherwise the same hand would be present twice in the IN files of two pairs. This is a practical rule but is not a constraint of the App that makes no control of the hand sequence.
Should we put all hands played by a pair into its IN file (regardless of NS or EW position), each time two pairs (e.g. pair 2 and 4 for hand 1) should decide who records that result inside the OUT file (i.e. OUT_2 or OUT_4). Should both pairs record the result, no big harm, if they record the same result, of course.
As you see, being an Howell tournament, pair 2 playes both in NS and in EW
While the input file on a table fixed on table 2 (IN_T2.txt) is
OUT file record fields are those of the input file plus:
played contract, plus or minus tricks, by whom, leading card, NS result, and the bidding sequence composed of bid and time interval in milliseconds (the first bid has time interval 0 by default). A + next to a bidding means that it was alerted.
For instance, the first three deals of the table 1 above produce this OUT file:
Please note that the third deal ended with All Pass
Moreover at the head of OUT files there is this row:
Latest nn AndroidId xxxxxxxxxxxxxxxxxxxx
nn is the number of the latest played hand, so that when you use the Continue! button in Home Page, the next hand is shown.
xxxxxxxxxxxxxxxxxxxx is an unique identifier of the used tablet/smartphone. It can help to avoid frauds during a tournament,
File OUT crypted
OUT files can be encrypted or clear text, based on To encrypt Preference.
Non encrypted files end with .txt (e.g. OUT_1.txt), while encrypted files end with _E.txt (e.g. OUT_1_E.txt).
Encryption is done with
- Java class chipher
- AES algorithm
- 128 bit key created by repeating the Secret Key four times
- Base64 encode
To decrypt a file is hence necessary to
- Base64 decode
- decrypt with AES algorithm and the same key