On 10, Feb 2005, at 7:24 AM, Chris Fant wrote:
Sounds like you need to incorporate some time management into the
program instead of blindly letting it play as long as it wants even if
it is low on time.
SlugGo plays to a specified search depth. Because this is a serial
search I can think of no way to speed this up beyond what we have
already done with hash tables, other than to make search depth
a time dependent variable.
It seems from the set of replies that computer Go wishes to retain
what I see an an artificial but generally accepted limitation of one
hour per program, with possible exceptions in some tournaments
which allow for byo-yomi. I see the point of the convenience factor
and have no choice but to either comply or not attend, but I do not
think it is a good thing for the evolution of computer Go. David
Fotland has said in an earlier thread that he is not really sure
what MFoG might do with the extra time, but SlugGo clearly uses
it to advantage and I have the data that proves it.
It looks to me like people are asking "what is the best blitz Go
program" rather than "what is the best Go program." That is
OK too, just a little different.
I was meaning to keep out of this, but I can't let that comment pass.