On Thu, 2007-01-11 at 07:52 -0500, Don Dailey wrote: > I agree that Gnugo was written in an absolute non-scalable style. > What > Gnugo does is continually upgrade from year to year. They are > making > their program scale in a painfully manual way.
I want to clarify what I said about Gnugo. I'm not being critical of this style - it's perfectly feasible to just upgrade often and keep up in this way. For instance if level 16 is now considered fairly optimal but just too slow, it might become the default level in a future release of gnugo in just a year or two - perhaps with algorithmic optimizations to speed this up further. But that's my point - by then and along with other improvements someone might say level 24 is best - and no doubt there would be other improvements to go along with this that makes it do more work. One could imagine a very clever engineer taking Gnugo 3.7.10 at level 16 and finding a way to make it run at 10 seconds per move. Whether this is possible or not - you get the point - it all comes down to making it "do more" in a given amount of time. Scalability is either explicit or implicit. - Don _______________________________________________ computer-go mailing list computer-go@computer-go.org http://www.computer-go.org/mailman/listinfo/computer-go/
