Author: Stuart Cracraft
Date: 08:29:30 10/25/04
Go up one level in this thread
On October 25, 2004 at 08:14:18, David B Weller wrote: >Hi Stuart, > >Well, one thing was that my main iterative search driver was calling search >WITHOUT null-move enabled, so null-move was never tried at ply=2. [only ply=3, >etc.] I am not totally convinced that it was that big a deal, however. I have one routine search() for all plies instead of the more standard searchroot() for ply == 0 and search() for ply == 1..N. Early in the program's history, I did not disable null move when ply == 0 but now do. I found that that plus another change fixed my PV. > >also, I had some code to try and 'help' outside passers, which was basically >adding a bunch of bogus values all througout.... > >and my 'material-imbalance' code had a severe error - > >BTW, do you acknowledge such things in your material+pst eval? [ie., material >imbalances and even bishop pairs] since they are really only material related >and so easily measured... Hope to. :-) Stuart
This page took 0 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.