Author: Geoff
Date: 15:42:25 06/04/03
Go up one level in this thread
Hello Michel
I tried that test with my work in progress engine
With Full position evaluation
-----------------------------
Test results for 300 Positions. Solved 231. Failed on 69
Total time for test suite 21:27 Minutes
Total nodes: 1,351,014,102
nps 1,049,739.
With Material Only evaluation
-----------------------------
Test results for 300 Positions. Solved 226. Failed on 74
Total time for test suite 21:11 Minutes
Total nodes: 1,658,896,846
nps 1,305,190
So for me at least it is slightly better with positional code in
Incidentally, I have a similar bit of code to yours, early in my eval
/* this is likely to cause a beta cutoff so dont bother working out
more accurately, return early */
if ( score > beta + 300)
return score;
The difference is though that I didn't do the same trick for alpha (wonder if I
should try it?) and that my threshold is double yours at 3 pawns
I also tried testing with my Null move code turned off. This gave
Without Null Move Searching
---------------------------
Test results for 300 Positions. Solved 206. Failed on 94
Total time for test suite 21:43 Minutes
Total nodes: 1,368,153,533
At least this gave an expected worsening of the result
I wanted to try this as my Null move searching feature from other tests seems to
increase depth but reduce playing strengh !!! Grrrrrrrrr !!!
Did you try the test with Null move turned off ? I would be interested to see
what effect that has on your numbers
regards Geoff
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.