Author: Ernst A. Heinz
Date: 11:30:33 05/18/00
Go up one level in this thread
Hi Blass, >I agree that this is not a bug because the decision to let Bxa7 was a design >decision but it is not clear that this decision was correct. As I said, I very much prefer the implementation of _general principles_ rather than the addition of ever more code for the handling of special cases. IMO, this is the correct design decision. But it does not make much sense to discuss the "trapped Bishop" phenomenon in more detail, unless we have some hard facts to support either point of view. >This is a position from the game Junior5.4-Crafty16.6 > >[D]r2nkb1r/pp1n2pp/8/1P1pp3/8/2P1B3/1P3PPP/RN2KB1R w KQkq - 0 1 > >Junior played the move 17.Rxa7 and was in trouble after Rxa7 18.Bxa7 b6 >Junior saved a draw because of the fact that crafty did not use tablebases so >Junior could escape to a KR vs KRN endgame. > >I do not think that Rxa7 is a good move >The game was played with p200 under Junior5 interface(engine-engine game). > >Can your program avoid Rxa7? Yes, "DarkThought WCCC'99" locks onto Be2 in iteration #9 after less than a second. =Ernst=
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.