I agree with Uri but when I tested Trace 2 I came up against a fairly common problem... evaluation horizon effect...Steve Maughan wrote:
Here a position that's been discussed on Susan Polgar's blog (http://susanpolgar.blogspot.com/2008/01 ... stuff.html)
[d]8/8/7p/2p5/2P1K3/1kP1P3/8/8 w - -
It's a draw. But many of the top engines think that Kf5 wins for white. The engines that seem to have problems are Glaurung 2, Naum 2.2 and Rybka - Shredder and Hiarcs see that it's a draw. It's probably a position where the square of pawns rule breaks down. Anyway I thought it was of interest
Uri replied:
The main problem here is that glaurung does not see that the following is a draw
[d]4Q3/8/8/8/7K/8/1kp5/8 w - - 0 9
Uri
T2 understands that Uri's example is drawn - however, she avoids capturing the h pawn so that her KPKQ evaluation doesn't kick in and return a draw. In the original position she scores Kf5 as +6.75 @ 26 ply depth.
Also, mighty Rybka 2.3.2a gets to 25 ply and scores Kf5 as +7.29
Evaluation horizon effect is a pain in the a$$ to solve. If I write a KPPKQ recognizer the same horizon effect will occur when there is KPPPKQ on the board. ... so I have to write a KPPPPKQ ... and so on...
Turn off EGBB and EGTB and see if your engine can solve it.
Any ideas on how to fix this one?
Ross