Computer Chess Club Archives


Search

Terms

Messages

Subject: Re: good time usage of programs

Author: Roland Pfister

Date: 04:05:04 06/02/98

Go up one level in this thread



On June 02, 1998 at 06:49:16, Inmann Werner wrote:

>Making programs faster is making them playing better.(?!)
>OK
>But in a match, if there is a time limit, it is important, that the
>program thinks long at the right time, and not, when everything is
>clear.
>But to implement that is more then difficult. When is a move "clear"?

If it is the only legal move :-)

In my program: when all other moves lose ( mate score against program).

>Maybe deeper, there is a fine combination. When should the program
>take time to look deeper?
>
>any suggestion, which are common?

Usually when the program smells trouble (i.e. fail low, or score
continually
falling). But often it is too late :-(

Bob Hyatt told us that Deep Blue recognizes trouble when the shape
of the search tree does not look "normal" and it goes into panic mode
then.

Roland

P.S.
Don't look deeper when your score is especially good. Walter Bannermann
had implemented that in Ananse and lost a won position on time :-)



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.