![]() (UCI does not specify any on-disk format for the opening book different UIs usually have their own, proprietary formats.) Also, the user interface may handle endgame tablebases if the engine does not support it itself, although this is often better handled in the engine, as having tablebase information can be useful to consider a possible future position. ![]() Most notably, the opening book is usually expected to be handled by the interface, by simply selecting moves to play until it is out of book, and only then starting up the engine for calculation in the resulting position. ![]() Like the latter, it is free to use without license fees.Ĭustomarily, UCI assigns some tasks to the user interface that have traditionally been handled by the engine itself. It was designed and released by Rudolf Huber and Stefan Meyer-Kahlen, the author of Shredder, in November 2000, and can be seen as a rival to the older XBoard/ WinBoard Communication protocol. (UCI) is an open communication protocol that enables a chess program's engine to communicate with its user interface. As of 2006, there are more than 300 chess engines (including GNU Chess and Crafty) and 30 chess interface programs (including XBoard itself and eboard) that support this protocol with varying degrees of compatibility.Īs of 2008 work is being done to update the Chess Engine Communication Protocol with some convenient features such as the ability to set memory usage and the number of search threads (the latter is essential for Symmetric multiprocessing architectures). The protocol also supports three different styles of time control: conventional clocks, incremental clocks (Fischer Delay), and exact seconds per move. Since its early days, the protocol has grown more robust and now supports standard chess games along with various chess variants including Wild Castle, No Castle, Fischer Random, Bughouse, Crazyhouse, Losers, Suicide, Give Away, Two Kings, Kriegspiel, Atomic, and Three Check. XBoard, using the protocol, "wrapped around" GNU Chess by feeding the engine the expected text input, parsing the text output, and presenting this information on a graphical chess board. ![]() In fact, the first version of this protocol is nothing more than the behavior of GNU Chess's command line interface. ![]() It was initially intended to only communicate with the GNU Chess engine which only accepted text input and produced text output. It was designed by Tim Mann, the author of XBoard. The Chess Engine Communication Protocol is an open communication protocol that enables a chess engine to communicate with its user interface. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |