25,161
edits
Changes
no edit summary
During testing the engines should ideally play the same style of openings they would play in a normal tournament, so not to optimize them for different types of positions. One option is to use the engines own [[Opening Book|opening book]] or one can use [[Test-Positions#OpeningSuites|opening suites]], a set of quiet test positions. In the latter case the same opening suit would be used for each tournament conducted and furthermore each position is played a second time with colors reversed. With these measures one can try to minimize the disparity between tests caused by different openings.
==InterfacesTournament Manager== Free [[GUIUser Interface|graphical user User interfaces]] or [[CLI|command line tools]] for [[UCI]] and [[Chess Engine Communication Protocol]] compatible engines in engine-engine matches are:* mentioned under [[Amoeba#TournamentManager|Amoeba Tournament Manager]]* [[Arena]] by [[Martin Blume]] <ref>[http://www.playwitharena.com/ Free chess graphical user interface (GUI) Arena for chess engines]</ref>* [[Cute Chess]] by [[Arto Jonsson]] and [[Ilari Pihlajisto]]: [[Cutechess-cli]]* [[LittleBlitzer]] by [[Nathan Thom]] <ref>[http://www.talkchess.com/forum/viewtopic.php?t=35249 Fast Games] by [[Manuel Diaz]], [[CCC]], July 02, 2010</ref>
==Frameworks==
