Author: Scott Gasch
Date: 19:06:11 10/02/05
Go up one level in this thread
On October 01, 2005 at 08:13:00, Michael Diosi wrote: > 8/8/pppppppK/NBBR1NRp/nbbrqnrP/PPPPPPPk/8/6Q1 w - - 0 1 Monsoon takes hours to see this because it plays the captures first and then gets stuck in the qsearch swapping off all the other trades. This is a really interesting position and I wonder how other engines are solving it so quickly. Naturally if you search checks before captures you will solve this but you won't have as efficient a search tree. Is there some logic for "that's a really dangerous check!" other people have used? Or is it more like "at depth=1 we are 30 ply deep in qsearch, stop already!" Scott
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.