RULES:
Site: The Internet Chess Club (as always)
Tournament Director: Peter Skinner
Date: March 21-22, 2009
Registration Deadlines: March 15, 2009
Time controls: 50 + 3
Rounds: 9 Round Swiss.
Round Times:Saturday: 7:00am 9:00am 11:00am 1:00pm 3:00pm
Sunday: 7:00am 9:00am 11:00am 1:00pm
Blitz Tournament to follow regular event (Click on link to left for information)
Please be sure to check for time zone differences!
Based on ICC's "date" command. (Time zone is EST)
All games to be played in one weekend:
5 games on Saturday
4 games on Sunday
In the event of a tie situation:
There will be co-winners awarded.
1. No manually operated programs, and all programs must kibitz their evaluation, and book moves/TB hits if possible. Providing as much information as possible for the viewers and participants is key here. It should also be noted that 1-3 lines of text is sufficient. No need to scroll out an entire page.
2a. In the event of a disconnection, the party will be given 5 minutes to return to complete the game and no more than 2 disconnections per game will be allowed. On the third time, the game will be a forfeit.
2b. In the event that a program can not continue a game due to interface or program issues, it will forfeit the game. Under no circumstances will a new game be formed or the game restarted.
2c. If a program is not open for matches or arrives late for a scheduled round, the game will be played under time odds. The amount of time that their opponent has waited to begin will be deducted from the clock at the game start.
3a. Each participant (engine) must an original work. No entry can contain code from another program, or be a "clone" of another program. This includes any "personality" settings of an originating program.
3b. Any engine that is found to be "clone" of another program or close to it (e.g. engine output, pondering information, analysis of positions) will be declared void by the Tournament Director after seeking advice from notable sources.
3c. The Tournament Director can ask for the compiled executable and corresponding source to the participating version of an engine to let it be examined by the previous mentioned notable sources. If the author of the engine that is suspect were to refuse to confirm the originality of his own work, the engine and the author will be disqualified from the CCT, and will no longer be able to participate in future events.
Only the original author, Operator or a team member of the original program may enter and operate.
4. Participants can use any hardware they can bring. Participants choosing to use remotely located hardware are recommended to have a suitable back up solution in the event there is an uncorrectable malfunction.
5. In the event that there is a late withdrawal or uneven amounts of players, the TD can substitute a program in place of the departing entrant to keep the numbered entries the same. And to avoid a bye round.
6. Seeding will be calculated on results from previous official tournaments. WCCC/Leiden/IPCCC/CCT/Testing Groups.
7. Any account that enters into the CCT will be given a 1 month account. If the author is operating the program for the entire tournament the account will be granted "free" status. For info, Contact the TD.
8. If a team has donated hardware for the event, promotional advertising in the form of a link to the sponsoring vendor will be provided. This will be placed under the hardware section of the "hardware" information. Promotional links will also be provided to other sponsors of the event if needed. All sponsors may also provide a short business profile and banner/button to be listed under the "Sponsors" page.
9. To enter, you need to be an established author.
This means that a program of yours must have a track record in some public environment such as previous official tournaments or main testing sites (CCRL, Open War etc).
Ways to establish yourself as a recognized author are:
*If Private, your engine should have an history of official tournament participation (World champs, ACCA, Previous CCT, Paderborn etc)
*If private, send the engine to the testing team to get their approval or release of the engine to the public.
**All new engine authors undergo this screening test, so It's normal.