Author: Daniel Clausen
Date: 11:00:13 12/03/02
Go up one level in this thread
On December 03, 2002 at 13:44:21, Colin Frayn wrote: >Here's an interedting position that arose in an ICC game between Beowulf and a >human player. it's one of those positions where Beowulf knows it's behind, but >can't possibly realise how bad his position is because he doesn't realise how >his h7 rook is utterly trapped. > >[D]r4k2/2R2p1r/4pBp1/4P2p/pR3P1P/Pb2K1P1/8/8 b - - > >I'm not sure how to get round this without adding in some hideously slow code. >I already have mobility code in for the rook but then it's difficult to >distinguish between a rook that's in a nice defensive position that it could get >out of and which will transform itself into an open file fairly quickly after a >pawn exchange, and something like this where there is no sequence of moves to >retrieve the rook from its corner. > >Cheers, >Col I think this is a good example, where a sophisticated root-evaluation could be of some help. Of course it would be nicer, if the engine would recognize this as a bad position for black during the search already, so it could avoid the position in the first place. But still, a good root-evaluation could at least help here to guide the search a bit from this position and help to avoid exchanging the only active rook and definitely be in a lost position afterwards... maybe the position is lost already anyway, but.. hope you get the idea :) Sargon
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.