Author: Robert Hyatt
Date: 20:01:10 04/23/02
Go up one level in this thread
On April 23, 2002 at 20:36:23, Slater Wold wrote: >I saw this for the first time the last nite; from an autoplayed game: > >Black(15): Rac8 [pondering] > time limit 2:55 (20:28) > nss depth time score variation (8) > 9 11.02 -0.05 16. Na4 Qd8 17. Nc5 Bxc5 18. dxc5 e5 > 19. Bb5 d4 20. Bg5 h6 > 9 1:00 0.11 16. Qd2 Qd8 17. Rac1 Qe7 18. Bf4 Bxf4 > 19. Qxf4 Nh5 20. Qg4 Qf7 > (3) 9-> 1:59 0.11 16. Qd2 Qd8 17. Rac1 Qe7 18. Bf4 Bxf4 > 19. Qxf4 Nh5 20. Qg4 Qf7 >Black(15): a8c8 >predicted move made. >**bad move from hash table, ply=11** > time=2:55 cpu=199% mat=0 n=257159262 fh=98% nps=1463k > ext-> chk=3574490 cap=1436502 pp=135962 1rep=240170 mate=0 sing=0 > predicted=15 nodes=257159262 evals=0 > endgame tablebase-> probes done=0 successful=0 > hashing-> trans/ref=24% pawn=99% used=99% > SMP-> split=66 stop=9 data=5/32 cpu=5:50 elap=2:55 > time used: 1:59 > > >I understand the error, but not what could be causing it. > >This is the version with SE, and no null move. Other than that, it's fairly >untouched. > > >Thanks! There is a 50% chance it was just a hash signature collision. Two different chess positions produced the same hash signature. The move in that hash entry was unfortunately illegal, which was reported above. I just checked the last 300 logs I have and I didn't see any. It is therefore possible that the SE implementation stored an invalid move directly, rather than having a key signature collision... Which it was would be impossible to say unless you can reproduce it...
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.