Author: Kurt Utzinger
Date: 13:31:39 02/02/06
Go up one level in this thread
On February 02, 2006 at 16:13:02, George Speight wrote:
>
>Hi, Kurt. Maybe i am missing your point. But this took place in the game and i
>couldnt control his time. Juniors 33rd move as black busted him- i cant much see
>aworse choice. But the point of the matter is that after he made that move,
>Hiarcs evaluated his position as up over 7 points, and Junior still had it
>analyzed as even. Did he not see he was busted! I went on and analyzed the
>position after 33 and let Junior have white, and he saw Bxe4 with no problem.
>But as black he seemed to have no clue he was finished. Regards, George
Hi George
I don't see the point. As explained, Junior 9 needs some more
time than taken in the game to realize that 33...Be4 is wrong.
On the other hand, after 34.Bxe4 Junior 9 soon sees that Black's
position is busted (analysis below). It is quite normal that
engines handle a specific position very differently and in
extreme cases engine_A finds a move hundred (sometimes even
thousand) times faster than engine_B. The example given by
you is nothing special for me.
Best regards
Kurt
[D]8/1p1q3k/p3pBp1/4P2p/Pn2B3/1P2Q3/4K1PP/R2r4 b - - 0 1
Analysis by Junior 9:
34...Rxa1 35.Bxg6+ Kxg6 36.Qe4+ Kh6 37.Qxb4
= (-0.19) Depth: 3 00:00:00
34...Rxa1!
³ (-0.49) Depth: 6 00:00:00 14kN
34...Rxa1 35.Bxg6+ Kg8 36.Qg5 Qd1+ 37.Kf2 Qg1+ 38.Kg3 Qe1+ 39.Kh3 Qc3+ 40.Kh4
Rd1
³ (-0.65) Depth: 9 00:00:00 531kN
34...Rxa1 35.Bxg6+ Kg8 36.Qg5 Qd1+ 37.Kf2 Qg4 38.Qxg4 hxg4 39.Kg3 Kf8 40.Kxg4
² (0.44) Depth: 12 00:00:04 5190kN
34...Rxa1 35.Bxg6+ Kg8 36.Bb1 Kf7 37.Qg5 Ra2+ 38.Ke1 Nd3+ 39.Bxd3 Ra1+ 40.Ke2
Ra2+ 41.Ke3 h4
+- (2.66) Depth: 14 00:00:13 14902kN
34...Rxa1 35.Bxg6+ Kg8 36.Bb1 Kf7 37.Qg5 Ra2+ 38.Ke1 Qd2+ 39.Qxd2 Rxd2 40.Kxd2
b5
+- (6.16) Depth: 17 00:00:57 56427kN
(Utzinger, 02.02.2006)
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.