Author: Uri Blass
Date: 11:36:01 12/07/02
Go up one level in this thread
On December 07, 2002 at 14:21:46, Mike S. wrote: >On December 07, 2002 at 12:04:46, Colin Frayn wrote: > >>I've fixed the problem with recognising trapped rooks... sort of. Beowulf now >>recognises the following positions (and others like them) as completely trapped >>rooks (and penalises them based on game stage); > >In the CSS forum, this interesting postion was posted today: >[D]6k1/4pp1p/3p2p1/7n/p3P3/r4P2/P1PK2P1/1R5R w - - 0 28 >Kozirev - Varavin [B77], Omsk 1996 >28.Rxh5!! gxh5 29.Rb2 e6 30.c3 d5 31.exd5 exd5 32.Kd3 Kf8 33.Re2 f6 34.Kd4 Kf7 >35.Rc2 Ke6 36.Kc5 d4 37.Kxd4 1-0 > >The rook at a3 is trapped, and the wK is going to capture it. White must play >carefully at move 33 (Re2), to prevent Black's king from blocking the white >King's path. > >(First tests indicate that this is a tough one; I just hope Rxh5 isn't >refuteable.) The question is if Rxh5 is needed. The rook seems to be trapped even without it. At these moments Movei analyze the position after Rxh5 gxh5 Rb2 Here is the last line: depth=17 -0.20 e7e6 c2c3 d6d5 b2c2 g8f8 d2c1 d5d4 c1b2 a3c3 c2c3 d4c3 b2c3 f8e7 c3b4 h5h4 b4a4 e6e5 a4b4 e7d6 Nodes: 77079163 NPS: 237707 Time: 00:05:24.26 Uri
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.