Author: Peter Skinner
Date: 11:00:42 01/21/04
This morning Robert released a new update to the Crafty 19.9 source, and I have compiled it for those that can not compile on their own machines. I have begun a new way of compiling the source, and it has produced a speedup of around 5%. It is not much, but I will take all I can get. http://members.shaw.ca/craftychess/wcrafty1994.zip Here is the changes in main.c for those interested: 19.9 two new pieces of code submitted by Alexander Wagner. the first * * adds speech to crafty for unix users. /opt/chess/sounds needs to * * exist and the common/sounds.tar.gz file needs to be untarred in * * directory. "speech on*off" controls it. a new annotatet command * * outputs the annotated file in LaTeX format for those that prefer * * that platform. lots of source reformatting to make indenting and * * other things more consistent, using the unix "indent" utility. * * singular extension (simplistic approach) has been added and needs * * -DSINGULAR to activate it. once it has been compiled in, you can * * turn it on/off by setting the singular extension depth using the * * ext command. default is on if you compile it in. ext/sing=0 * * disable it. changes to non-COMPACT_ATTACKS code to shrink the * * array sizes. this was done primarily for the Opteron where the * * COMPACT_ATTACKS stuff was a bit slower than the direct look-up * * approach. this change reduced the table sizes by 75%. a small * * change to Evaluate() to better handle the 50-move draw problem. * * what used to happen was when the counter hit 100 (100 plies since * * last capture or pawn push) the score just dumped to DrawScore() * * instantly. it was possible that by the time the draw was seen, * * it was too late to do anything to avoid it without wrecking the * * position. What happens now is that once the 50-move counter * * reaches 80 plies (40 moves by both sides with no pawn push or * * capture) the score starts dropping toward DrawScore() no matter * * which side is winning. Dave Slate called this a "weariness * * factor" in that after playing 40 moves with no progress, the * * evaluation shows that the program is getting "weary". the idea * * is that the score starts to slip over the last 10 moves by each * * side to that if either can do something to reset the counter, * * they will do it sooner rather than later.
This page took 0.01 seconds to execute
Last modified: Thu, 15 Apr 21 08:11:13 -0700
Current Computer Chess Club Forums at Talkchess. This site by Sean Mintz.