Re: [computer-go] Computer Go tournament at EGF

[Don Dailey <drd@xxxxxxx>]

>  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.

You could speed it up by reducing the search depth.   

This is just my opinion, but I really think the best thing for
computer Go isn't to progressively slow down the tournaments (where
does it end?) to accomodate one player, but to be creative and find
ways to conform to realistic time controls.

It's very possible someone will come along after you with an algorithm
that is even slower and talk about how the time control is unfair to
them.  Again, where does it end?  As already expressed, the current
time control seems to be viewed as bordering on too slow.

> 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.

Every tournaments has rules and they are not necessary "artifical" or
impose "limitation" because they are not convienent for me or you.  In
my view, your programming system for Go is the one with limitations
(which it should be possible to overcome if the idea is valid.)   


   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.

   As above, I have figured out a way to force SlugGo to play faster
   and it is likely that the effect upon playing strength will be that it
   plays weaker. I have seen enough SlugGo games to be sure that
   it will play differently.

David, I think that a truly well engineered and scalable Go program
SHOULD play worse when forced to play faster.  Personally (and maybe
because I come from the chess world), it's just not convincing or
impressive seeing a program play better given more time.  In fact, I
believe my own program (as bad as it is) would beat every non-scalable
program out there if it wasn't "artifically restricted" by this silly
thing called time.

- Don


   Cheers,
   David


   _______________________________________________
   computer-go mailing list
   computer-go@xxxxxxxxxxxxxxxxx
   http://www.computer-go.org/mailman/listinfo/computer-go/

_______________________________________________
computer-go mailing list
computer-go@xxxxxxxxxxxxxxxxx
http://www.computer-go.org/mailman/listinfo/computer-go/