Author: Jeremiah Penery
Date: 16:37:13 12/03/03
Go up one level in this thread
On December 03, 2003 at 16:22:27, Robert Hyatt wrote: >On December 03, 2003 at 15:54:45, Tord Romstad wrote: > >>On December 03, 2003 at 14:59:03, Robert Hyatt wrote: >> >>>=====================10 seconds per position======================== >>>test results summary: >>> >>>total positions searched.......... 300 >>>number right...................... 299 >> >>That's really impressive, even considering the fast hardware. The last >>time I tried, I got 289/300 at 1 second/position, 293/300 at 3 seconds, >>294/300 at 5 seconds, 295/300 at 10 seconds, and 298/300 at 20 seconds. >> >>The remaining two positions, number 100 and 230, are *never* solved. >>I can let my program analyse for hours, but it still doesn't find >>the solutions. In both positions, it thinks it is winning, but >>never finds the right moves. > >I have gotten 230 in the past, but when I made some passed pawn changes of >some sort, it went away. But even back then it took several minutes to choose >the rook toss... If you compile with the #define DETECTDRAW it will find almost instantly that any move other than Rb4 is a blocked position draw. :)
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.