Author: Uri Blass
Date: 10:49:40 12/25/02
Go up one level in this thread
On December 25, 2002 at 13:42:13, Kurt Utzinger wrote: >On December 25, 2002 at 13:09:45, Sune Larsson wrote: > >> >> [D]5rk1/1ppq1rb1/p2p1nn1/3Pp3/2P1Ppp1/PPN3P1/3BQPB1/2R2RK1 w - - 0 25 >> >> >> This position happened in a blitzgame of mine vs CM 9000Utz12 (white). >> It's no longer a question of building a slow attack - instead it's already >> there, in full bloom. Or, another way to put it, white has nothing and >> black has everything. So, how do the programs evaluate such a position >> with some time to think? A few results: >> >> >> CM 9000Utz12 25.Qd3 -0.15 Ply 14 64 Mb hash >> Shredder PB 25.Qd3 -0.28 Ply 14 128 Mb hash >> Hiarcs 8 25.Qd3 -0.55 Ply 13 128 Mb hash >> Fritz 8 25.Qd3 -0.59 Ply 14 128 Mb hash >> Ruffian 25.Qd3 -0.69 Ply 14 128 Mb hash >> Chess Tiger14 25.Bh1 -1.50 Ply 14 96 Mb hash >> GambitTiger 2 25.Qd3 -2.26 Ply 14 96 Mb hash >> >> >> It was with utmost effort that CM finally realized that it actually >> is *worse* in the diagram position... With a tiny -0.15. CM Utzinger >> has achived great results in comp-comp games and perhaps it's possible >> to adjust the settings in a way that CM sees the danger?! King Safety? >> >> I'm curious of the evals from new programs like Chess Tiger 15, Shredder 7 >> and maybe also Schachfreund Utzinger's latest CM personality (a very promising >> one!)?! The whole game below. > >Utzinger,K - Shredder 7 >5rk1/1ppq1rb1/p2p1nn1/3Pp3/2P1Ppp1/PPN3P1/3BQPB1/2R2RK1 w - - 0 1 > >Analysis by Shredder 7: [P4 1.8/64 MB hash] > >1.gxf4 exf4 2.e5 dxe5 > = (-0.01) Tiefe: 1/2 00:00:00 >1.gxf4 exf4 2.e5 dxe5 > = (-0.01) Tiefe: 3/13 00:00:00 >1.gxf4 exf4 2.e5 dxe5 > = (-0.01) Tiefe: 3/13 00:00:00 >1.gxf4 exf4 2.e5 dxe5 > = (-0.01) Tiefe: 3/13 00:00:00 >1.gxf4 exf4 2.e5 dxe5 > = (-0.01) Tiefe: 3/13 00:00:00 >1.gxf4 exf4 2.e5 dxe5 > = (-0.01) Tiefe: 3/13 00:00:00 >1.gxf4 exf4 2.e5 dxe5 > = (-0.01) Tiefe: 3/13 00:00:00 >1.gxf4 exf4 2.e5 dxe5 > = (-0.01) Tiefe: 3/13 00:00:00 >1.gxf4 exf4 2.e5 dxe5 > = (-0.01) Tiefe: 3/13 00:00:00 >1.gxf4 exf4 2.e5 dxe5 > = (-0.01) Tiefe: 3/13 00:00:00 >1.gxf4 exf4 2.e5 dxe5 > = (-0.01) Tiefe: 3/13 00:00:00 >1.gxf4 exf4 2.e5 dxe5 > = (-0.01) Tiefe: 3/13 00:00:00 >1.gxf4 exf4 2.e5 dxe5 > = (-0.01) Tiefe: 3/13 00:00:00 >1.gxf4 exf4 2.f3 g3 3.Dd3 > = (-0.11) Tiefe: 4/12 00:00:00 >1.gxf4 Sxf4 2.Lxf4 exf4 3.Dd3 Te8 > ³ (-0.36) Tiefe: 5/16 00:00:00 >1.gxf4 Sxf4 2.Lxf4 exf4 3.f3 Te8 4.Dd3 gxf3 5.Lxf3 > ³ (-0.51) Tiefe: 5/16 00:00:00 >1.gxf4 Sxf4 2.Lxf4 exf4 3.f3 Te8 4.c5 dxc5 > ³ (-0.67) Tiefe: 6/13 00:00:00 >1.Dd3 f3 2.Lh1 Te8 > ³ (-0.66) Tiefe: 6/13 00:00:00 >1.Dd3 f3 2.Lh1 Sh5 3.De3 De7 4.Dg5 Dxg5 5.Lxg5 > ³ (-0.65) Tiefe: 6/15 00:00:00 >1.Dd3 Sh5 2.Lh1 fxg3 3.fxg3 Txf1+ 4.Txf1 Txf1+ 5.Kxf1 Sxg3+ 6.Dxg3 Df5+ 7.exf5 > ³ (-0.55) Tiefe: 7/19 00:00:00 81kN >1.Lh1 Sh5 2.Dd3 fxg3 3.fxg3 Txf1+ 4.Txf1 Txf1+ 5.Kxf1 Df5+ 6.exf5 Sxg3+ 7.Dxg3 > ³ (-0.54) Tiefe: 7/19 00:00:00 107kN >1.Lh1 f3 2.De3 Sh7 3.c5 Tc8 4.Tfe1 > ³ (-0.44) Tiefe: 7/19 00:00:00 127kN >1.Lh1 De7 2.Dd1 f3 3.Lg5 Te8 4.Te1 Dd7 > ³ (-0.49) Tiefe: 8/20 00:00:01 253kN >1.Lh1 Sh5 2.Dd3 c5 3.dxc6 bxc6 4.c5 dxc5 5.Dxd7 Txd7 > ³ (-0.55) Tiefe: 9/25 00:00:02 474kN >1.Lh1 Sh5 2.Dd3 De7 3.b4 f3 4.De3 Tb8 5.c5 Tff8 6.cxd6 cxd6 > ³ (-0.55) Tiefe: 10/28 00:00:04 981kN >1.Lh1 Sh5 2.Dd3 De7 3.b4 f3 4.De3 Tb8 5.c5 Tff8 6.cxd6 cxd6 > ³ (-0.55) Tiefe: 11/29 00:00:08 1814kN >1.Lh1 Lh6 2.Dd1 Th7 3.gxf4 Sxf4 4.f3 gxf3 5.Dxf3 S6xd5 6.Sb5 axb5 7.Dg2+ Sxg2 >8.Txf8+ Kxf8 > µ (-0.80) Tiefe: 12/28 00:00:29 6599kN >1.Lh1 Lh6 2.c5 Th7 3.Dd3 f3 4.cxd6 cxd6 5.Tfe1 Lxd2 6.b4 Lxc1 > µ (-1.23) Tiefe: 12/32 00:00:37 8530kN >1.Dd3 fxg3 2.Dxg3 Te8 > µ (-1.22) Tiefe: 12/32 00:00:38 8690kN >1.Dd3 fxg3 2.Dxg3 Te8 3.Tb1 Sh5 4.Dh2 g3 5.Dxh5 gxf2+ 6.Txf2 Dh3 > µ (-0.87) Tiefe: 12/32 00:00:39 9004kN >1.Dd3 Sh5 2.Lh1 De7 3.b4 Td8 4.b5 axb5 5.cxb5 f3 6.b6 > ³ (-0.52) Tiefe: 12/37 00:01:28 19900kN >1.Dd3 f3 2.Lh1 Ta8 3.De3 Sh7 4.b4 Tff8 > ³ (-0.50) Tiefe: 13/33 00:02:22 31844kN >1.Dd3 f3 2.Lh1 Lh8 3.Lh6 Th7 4.Lxf8 Txh1+ 5.Kxh1 Dh7+ 6.Lh6 Dxh6+ 7.Kg1 Dh3 >8.Sb5 axb5 9.Ta1 > µ (-0.75) Tiefe: 14/30 00:03:04 41185kN >1.Dd3 f3 2.Lh1 Lh8 3.Lh6 Th7 4.Lxf8 Txh1+ 5.Kxh1 Dh7+ 6.Lh6 Dxh6+ 7.Kg1 Dh3 >8.Sb5 axb5 9.c5 > µ (-1.25) Tiefe: 14/30 00:03:28 46863kN >1.Dd3 f3 2.Lh1 Lh8 3.c5 Th7 4.Sd1 Th5 5.Se3 Dh7 6.b4 > µ (-1.32) Tiefe: 14/34 00:03:53 52897kN >1.Dd1 fxg3 2.fxg3 Sh5 3.Txf7 Dxf7 4.Le3 Sxg3 5.Dxg4 Df2+ > µ (-1.31) Tiefe: 14/35 00:06:31 88982kN >1.Dd1 f3 2.Lh1 Lh8 3.Lh6 Th7 4.Lxf8 Txh1+ 5.Kxh1 Dh7+ 6.Lh6 Dxh6+ 7.Kg1 Dh3 8.c5 >Dg2# > µ (-1.31) Tiefe: 14/35 00:06:48 92856kN > >(Utzinger, MyTown 25.12.2002) shredder7 is not a fast searcher so I do not understand why the engine is so lazy not to evaluate if the final position is mate. shredder7 gives a main line when the last move is mate but evaluates the position as only 1.31 against white. Movei had a big fail low at depth 15 and here is the last analysis of movei(I believe that there may be a bug in the last moves of the pv of movei but movei is not a proffesional program. In aby case movei has no problem to evaluate mate positions correctly because number of legal moves is part of movei's evaluation. 14 -20 59308 90417654 e2d3 f4f3 g2h1 f8c8 d3e3 g6e7 f1e1 f7f8 e3d3 c7c6 d2g5 c6d 5 e4d5 e7f5 15 -68 146134 219464291 e2d3 g7h8 f1e1 f4f3 d2h6 f3g2 h6f8 f7f8 g1g2 h8g7 e1h1 c 7c5 d3d2 b7b5 g2g1 b5c4 b3c4 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.