Pretournament Check List

Discussion of chess software programming and technical issues.

Moderator: Ras

CRoberson
Posts: 2091
Joined: Mon Mar 13, 2006 2:31 am
Location: North Carolina, USA

Pretournament Check List

Post by CRoberson »

In todays ACCA tournament, I went through first several rounds with
the hashtable size set way too low. Quite the accident. I had a HD
failure last night so I was rather busy this morning.

So, I decided to create a Pretournament checklist so that such
things don't happen (or happen at lower frequency).

Here is what I have thus far for the program:

Code: Select all

     1) Hashtable size
     2) Computer clock speed (OC)
     3) Opening Book
     4) Compile options of last build (partly from a comment BoB H made).
     5) Run a test game to see that all is installed correctly
     6) Recheck Timer algorithm and equations - I experiment with this lots
For the HW:

Code: Select all

     1) Test the network
     2) Open up computer and blow out the dust
     3) Blow out the dust on network equipment (Experience from Andrew Williams)
     4) All is plugged into the UPS
So, do any of you have something to add to the list?
User avatar
Zach Wegner
Posts: 1922
Joined: Thu Mar 09, 2006 12:51 am
Location: Earth

Re: Pretournament Check List

Post by Zach Wegner »

CRoberson wrote:So, do any of you have something to add to the list?
[bitterness reason="CCT10"]Wake up on time.[/bitterness]
F. Bluemers
Posts: 880
Joined: Thu Mar 09, 2006 11:21 pm
Location: Nederland

Re: Pretournament Check List

Post by F. Bluemers »

CRoberson wrote:In todays ACCA tournament, I went through first several rounds with
the hashtable size set way too low. Quite the accident. I had a HD
failure last night so I was rather busy this morning.

So, I decided to create a Pretournament checklist so that such
things don't happen (or happen at lower frequency).

Here is what I have thus far for the program:

Code: Select all

     1) Hashtable size
     2) Computer clock speed (OC)
     3) Opening Book
     4) Compile options of last build (partly from a comment BoB H made).
     5) Run a test game to see that all is installed correctly
     6) Recheck Timer algorithm and equations - I experiment with this lots
For the HW:

Code: Select all

     1) Test the network
     2) Open up computer and blow out the dust
     3) Blow out the dust on network equipment (Experience from Andrew Williams)
     4) All is plugged into the UPS
So, do any of you have something to add to the list?
check whats running in the background.
especially when running on normally unusual times.
There might be an automatic virus scan you forgot about.
Also there might be stuff like the daily(or should i say nigthly) winDOS vista making new restore points.
Linux might have other suprises in store for you.
Best
Fonzy