Computer Chess Club Archives


Search

Terms

Messages

Subject: Re: Crafty Bug?

Author: Robert Hyatt

Date: 07:36:26 08/14/02

Go up one level in this thread


On August 14, 2002 at 01:01:57, Slater Wold wrote:

>White(1): setboard 8/8/3pR1P1/2k5/8/1p1b4/7K/8 b - - 0 67
>Black(1): go
>end-game phase
>              clearing hash tables
>              time surplus   0.00  time limit 3:00 (3:00)
>         nss  depth   time  score   variation (1)
>starting thread 1
>         (4)    8->   0.39   0.01   1. ... Bxg6 2. Rxg6 <HT>
>         (3)    9     0.48   0.01   1. ... Bxg6 2. Rxg6 <HT>
>         (4)    9->   0.73   0.01   1. ... Bxg6 2. Rxg6 <HT>
>         (3)   10     0.97   0.01   1. ... Bxg6 2. Rxg6 <HT>
>         (4)   10->   1.67   0.01   1. ... Bxg6 2. Rxg6 <HT>
>         (3)   11     1.70   0.01   1. ... Bxg6 2. Rxg6 <HT>
>         (4)   11->   3.55   0.01   1. ... Bxg6 2. Rxg6 <HT>
>         (3)   12     3.55   0.01   1. ... Bxg6 2. Rxg6 <HT>
>         (4)   12->   7.45   0.01   1. ... Bxg6 2. Rxg6 <HT>
>         (3)   13     7.53   0.01   1. ... Bxg6 2. Rxg6 <HT>
>               13    21.12     ++   1. ... b2!!
>               13->   2:49  -0.38   1. ... b26
>              time=3:00  cpu=307%  mat=1  n=242037717  fh=94%  nps=1342k
>              ext-> chk=29936339 cap=78644 pp=227271 1rep=1144737 mate=32723
>              predicted=0  nodes=242037717  evals=21110434
>              endgame tablebase-> probes done=239240  successful=53187
>              SMP->  split=778  stop=81  data=9/32  cpu=9:13  elap=3:00
>
>Black(1): b2
>              time used:   3:00
>
>#1 - You should see b2 wins pretty much immediatly.  Sure, 21.12 seconds isn't
>bad, but imagine this on a PIII 600!  -0.38 isn't very convincing either.
>
>#2 - What's up with 13->   2:49  -0.38   1. ... b26  <//==- that?

That is just a display problem.  The _previous_ move searched had a 6 in
the third character.  When the search finished, the PV was one move long so
the screen didn't get overwritten far enough to remove the 6.  If you check
the log file, you won't see that...  It is caused by the way I display each
move as it is checked without moving the cursor to a new line...


>
>#3 - Any reason you can see why Crafty would take *forver* (even after this
>move) to see the win?

I haven't looked at it carefully, but it could be a null-move problem or
an eval problem...




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.