Author: Will Singleton
Date: 09:10:04 03/07/99
Go up one level in this thread
On March 07, 1999 at 05:39:53, David Blackman wrote: >On March 07, 1999 at 04:57:52, Dave Gomboc wrote: > >>My (not chess) playing software searches fine.. or so it seems, when I have an >>"extend on capture" setting of 0 ply, 1/3 ply, 1/2 ply, etc. But if I set it >> to 1 ply, I occasionally hit a position where boom! there goes the stack. >> >>I am wondering if this is endemic to extending by a full ply or not. >> >>Dave Gomboc > >In chess this shouldn't happen. I have actually tried this. It's not a winner, >but at least it works, and the stack doesn't blow out too badly. > >What game is it for? In chess you have a max of 30 or 31 captures in any given >line, so it's self limiting. I suppose some games might have much more material >to get rid of? > >Actually my chess program tests how deep it is in the tree. If it's more than >about 70 plies it prints a message to the log file, then just does a static eval >and returns. This might be useful for debugging this sort of problem. 70 ply? That would qualify, I think, as an instance of the tree blowing up. Remember, Dave was talking about extending the full-width search, not captures in the qsearch. But even so... I find in my program that unless the capture extensions are severely limited, then the whole thing slows down unacceptably. Will
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.