Computer Chess Club Archives


Search

Terms

Messages

Subject: Re: Hard position? revisited

Author: Pete Galati

Date: 12:30:36 01/03/01

Go up one level in this thread


On January 03, 2001 at 13:46:41, Pete Galati wrote:

>On January 03, 2001 at 04:04:30, Uri Blass wrote:
>
>>On January 03, 2001 at 03:35:57, Pete Galati wrote:
>>
>>>On January 02, 2001 at 02:45:27, Ferdinand S. Mosca wrote:
>>>
>>>>On January 02, 2001 at 01:24:15, Steve Timson wrote:
>>>>
>>>>>This position is from a game Chester played on ICC vs. a human.
>>>>>
>>>>>[D] 1r3rk1/pbqnnppp/4p3/2ppP3/p2P4/B1PB1N2/2P2PPP/R2QR1K1 w - - 0 15
>>>>>
>>>>>Chester's opponent played Bxh7 and went on to win.  Chester has a very hard time
>>>>>understanding this position.  It doesn't realize Bxh7 is a good move until a few
>>>>>moves down the resulting sequence (Bxh7 Kxh7 Ng5+ Kg6 and it sees the swing
>>>>>after Qg4).  How do other programs do here?  Do they see Bxh7 in a reasonable
>>>>>time period?
>>>>>
>>>>> - Steve
>>>>
>>>>
>>>>
>>>>Hi Steve,
>>>>
>>>>Yace on P3_450 found Bxh7 in less than 27 seconds.
>>>>This position is a bit hard for programs since it gives up material.
>>>>
>>>>Dinan
>>>
>>>With the Dos Comet on a Celeron700 in Windows, approx 18mb hash, it took 77
>>>seconds.  I have doubts that this is very difficult for a program at all.  [....]
>>
>>CometB27(64 mbytes hash under chessbase) had a fail low without solving it.
>>It is a bad point to stop it.
>>If you give Comet more time it is going to solve the fail low and see a negative
>>score for Bxh7+ and it is going to change its mind to Qd2
>>
>>Comet can find Bh7 again at depth 10 and it fail high again and again to get
>>+1.61 score after 4:47 on pIII800.
>>
>>It fails high again at depth 11 and it can see +1.97 score after 6:15 and +1.99
>>at depth 12 after 9:11.
>>It fails high again at depth 13 with score of +2.12 after 13:38
>>
>>I agree that the position is not very hard but your result for Comet is too
>>optimistic because you stopped it before it had an opportunity to see the
>>tactical reason.
>>
>>The times are not exactly correct and may be slightly smaller because the p800
>>did another task(this post)
>>
>>Uri
>
>Ok, if I remember to do it, I'll reboot into Dos and let Comet run with this
>position for an hour or two, see what it thinks then.
>
>Pete

Ok, not that this is a reasonable length of time for Cpmet to think about this,
but Comet now run from ME's Dos, which now gave it approx 60mb hashtables, I let
it run for approx 1 hour and 20 minutes, here's the results.  Just like you
said, it looked at Qd2 for a while around depth 9.

Pete

Comet-B.27    Wed Jan  3 12:55:07 2001

depth	score	  sec	  nodes		  pv
 1.	+0.19	    0	      947	 d3b5
 2.	+0.15	    0	     3466	 a3c5  d7c5  d4c5  c7c5  a1a4
 3.	+0.15	    0	    10709	 a3c5  d7c5  d4c5  c7c5  a1a4
 4.	+0.11	    0	    12140	 a3c5  d7c5  d4c5  f8c8  f3g5
 4.	+0.11	    0	    41242	 a3c5  d7c5  d4c5  f8c8  f3g5
 5.	+0.02	    0	    49891	 a3c5  d7c5  d4c5  f8c8  a1a4  c7c5  d1d2
 5.	+0.11	    0	    80031	 d1d2  f8e8  d4c5  e8c8  a3b4  d7c5  b4c5
 5.	+0.11	    1	   133031	 d1d2  f8e8  d4c5  e8c8  a3b4  d7c5  b4c5
 6.	+0.14	    2	   245899	 d1d2  f8e8  a3c5  d7c5  d4c5  c7a5  e1b1
 6.	+0.14	    4	   766414	 d1d2  f8e8  a3c5  d7c5  d4c5  c7a5  e1b1
 7.	+0.13	    7	  1067950	 d1d2  f8c8  e1b1  e7g6  a3c5  d7c5  d3g6
 7.	+0.13	   11	  1694460	 d1d2  f8c8  e1b1  e7g6  a3c5  d7c5  d3g6
 8.	+0.04	   23	  3131477	 d1d2  f8e8  e1b1  b7a8  d2g5  b8b1  a1b1
 8!	+0.26	   73	 11291621	 d3h7  g8h7  f3g5  h7h6  d1g4  e7g6  g5e6
 8!	+0.53	   74	 11626173	 d3h7  g8h7  f3g5  h7h6  d1g4  c5d4  a3e7
 8.	+0.56	   76	 12061079	 d3h7  g8h7  f3g5  h7g6  d1g4  f7f5  a3c1
 8.	+0.56	   76	 12088281	 d3h7  g8h7  f3g5  h7g6  d1g4  f7f5  a3c1
 9?	+0.42	   77	 12542751	 d3h7  g8h7  f3g5  h7g6  d1g4  f7f5  g4f5
 9?	+0.15	  102	 17642091	 d3h7  g8h7  d4c5
 9?	-0.12	  154	 25983659	 d3h7  g8h7  d4c5
 9.	+0.14	  188	 30209279	 d1d2  h7h6  d2f4  c7a5  d4c5  d7c5  a3b4
 9.	+0.14	  201	 32351345	 d1d2  h7h6  d2f4  c7a5  d4c5  d7c5  a3b4
10.	+0.09	  244	 37775643	 d1d2  h7h6  d4c5  d7c5  a3c5  c7c5  a1a4
10!	+0.27	  268	 42603683	 d3h7  g8h7  f3g5  h7g6  a3c5  d7c5  d1g4
10!	+0.54	  280	 45232202	 d3h7  g8h7  f3g5  h7h6  d1g4  c5d4  a3e7
10!	+0.81	  294	 48264401	 d3h7  g8h7  f3g5  h7h6  d1g4  c5d4  a3e7
10!	+1.08	  311	 52289875	 d3h7  g8h7  f3g5  h7h6  d1g4  c5d4  a3e7
10!	+1.35	  335	 58285894	 d3h7  g8h7  f3g5  h7h6  d1g4  c5d4  a3e7
10.	+1.61	  349	 61509841	 d3h7  g8h7  f3g5  h7g6  d1g4  f7f5  g4g3
10.	+1.61	  354	 62586980	 d3h7  g8h7  f3g5  h7g6  d1g4  f7f5  g4g3
11!	+1.74	  406	 76282183	 d3h7  g8h7  f3g5  h7g6  d1g4  f7f5  g4g3
11.	+1.98	  453	 87555011	 d3h7  g8h7  f3g5  h7g6  d1g4  f7f5  g4g3
11.	+1.98	  480	 93963060	 d3h7  g8h7  f3g5  h7g6  d1g4  f7f5  g4g3
12.	+1.99	  626	144196106	 d3h7  g8h7  f3g5  h7g6  d1g4  f7f5  g4g3
12.	+1.99	  737	178861765	 d3h7  g8h7  f3g5  h7g6  d1g4  f7f5  g4g3
13!	+2.12	  969	241916599	 d3h7  g8h7  f3g5  h7g6  d1g4  f7f5  g4g3
13!	+2.39	 1256	305331128	 d3h7  g8h7  f3g5  h7g6  d1g4  c5d4  a3e7
13?	+2.39	 1334	335165279	 d3h7  g8h7  f3g5  h7g6  d1g4  f7f5  g4g3
13.	+2.39	 1725	461035736	 d3h7  g8h7  f3g5  h7g6  d1g4  f7f5  g4g3
14!	+2.52	 2305	635182679	 d3h7  g8h7  f3g5  h7g6  d1g4  f7f5  g4g3
14?	+2.52	 4780	1557852759	 d3h7  g8h7  f3g5  h7g6  d1g4  f7f5  g4g3
14.	+2.52	 4783	1558715376	 d3h7  g8h7  f3g5  h7g6  d1g4  f7f5  g4g3

==> My Move: d3h7 in 79:59



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.