Author: Robert Hyatt
Date: 09:52:10 01/23/02
Go up one level in this thread
On January 23, 2002 at 05:24:35, Uri Blass wrote: >On January 22, 2002 at 19:27:41, K. Burcham wrote: > >>Amir when i run this line through Deep junior7, DJ7 cannot >>see what is going on. even at the depths below. >>none of my other programs do this. my other programs show >>the initial position eval as .0 >>so does DJ7. but with the first move, DJ7 still shows .0 through >>several moves. other programs show large eval change with first move >>of f5. > >I think that shredder is wrong here and after f5 the evaluation should be a draw >and the mistake is some moves later. > I agree. After f5 it is still a draw. f4 is a silly move after f5, but even after that it is still a draw... > >The problem with Junior is that Junior simply does not search positions that it >believes that they are drawn. >The problem is known for years but it seems that it is not important for >Amir to fix it. > >I can imagine some ways to fix at least most of the problems. >Here are 2 possible ideas: > >1)stop analyzing positions that are believed to be draw only if the remaining >depth is small enough. > >2)stop using insufficient material in some situations(for example >after seeing 0.00 evaluation and getting a big depth). > ><snipped> >> also can you explain the DJ7 eval at 67...g5---here DJ7 engine stops. >>kburcham > >67...g5 is the only legal move so Junior does not need to analyze. > >Uri It is also the move that turns that lousy rook pawn into a winning knight pawn. :)
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.