Author: Michael Neish
Date: 22:59:42 11/23/99
Go up one level in this thread
On November 24, 1999 at 01:41:45, Michael Neish wrote: > >>Then it struck me why Crafty saw it so fast. Anytime the black king got to the >>back rant, Crafty would see Qa8+ followed by Qxh8 winning a rook for white. >>Then it would hit the qsearch (or nullmove and hit the qsearch) where black has >>no good capture. The difference being that LambChop (which looks at checks in >>the qsearch) would hit the qsearch, and see Qb1+ forces checkmate. > If I may follow up my follow up (!) I'd like to ask those who don't include checks in their qsearch routines how they handle a potentially damaging check just outside the search horizon. In some test games my program twice fell foul of this fiendish manoeuvre, resulting in a lost piece. If you search deeper, then the deadly check can always come a ply later, so how do you handle it? Cheers, Mike.
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.