What to do when things go wrong with tsh.
Updated Sat Jan 21 09:13:37 EST 2006 for tsh 3.050.
It's possible that some OS/X browsers may download a non-executable version
of this file. If so, please contact me for instructions.
If you can't reach me, move your tsh folder to your home directory,
open a “Terminal” window,
enter the command “cd tsh-nnnn
”
replacing “nnnn
” with the version number
that you downloaded,
and finally enter the command
“chmod a+x osx*
” to mark the command
executable.
You can delete bad pairings using the “UnPairRound
” command,
edit scores using the
“EditScore
”
command
and delete bad scores using the
“DELETEscore
”
command.
See the command reference for the syntax
of those commands.
If you have made a serious error, you can manually revert to an earlier version of any tournament data (“.t”) file. tsh journals a copy of the tournament data file into a subdirectory or folder named "old" after each major change. Quit out of tsh, then look for the last good data file (either by checking the timestamps or inspecting the contents of the files), rename the bad “.t” file to “.t.bad” and put a copy of the journalled “.t.lotsofnumbers” file in its place as a new “.t” file.
You can also edit “.t” files using a text editor. If you do so, first quit from tsh, because tsh keeps an internal copy of its data that will overwrite any changes you make when tsh next updates its files.
If you are testing a new tsh feature, it’s possible that a program bug may put tsh into an infinite loop or dump core. In the former case, when tsh doesn’t give you a prompt, you’ll have to interrupt tsh and restart it. In OS/X and Unix, you interrupt terminal processes by pressing Control-C.
Some early versions of some pairings commands took a very long time to
run. It’s possible that some bugs remain undiscovered. If you
find that generating pairings in one particular situation takes
excessively long (more than a few seconds), you may interrupt
tsh, restart it, and then manually enter
a faster pairing command.
Allowing an extra repeat should in most cases substantially speed up
the pairings calculations, or you can use the
“PAIR
” command to manually pair key players
and then a regular command to pair the rest.
In any case, in the unlikely event that this happens to you, please
e-mail John a copy of the “.t” file involved.
As mentioned above, tsh journals its data after each major command, so if you are unsure about the condition of its files after a crash, revert to the last versions that were saved before the crash.
If you aren't sure what an error message means, look to see if it
has a code in [square brackets] at its end.
If so, use the
“HUH
”
command to ask for an explanation.
If not, contact John and ask him to add an explanation.
My phone number is (416) 876-7675. If you arrange with me beforehand, I’ll make sure that I’m easily reachable at that number during your tournament. If you didn’t prearrange my availability and you’re reading this because something has just gone unexpectedly wrong during a tournament, please try calling me anyway.