> code. The only thing that matters in the short term for making GNU Go > stronger is to catch up with the Monte Carlo development, especially > make the Monte Carlo code scale better to larger boards. Key ideas to > look into there are RAVE (rapid action value estimation), > progressive widening, and improved move ordering.
And then rename it to be YAMP "Yet Another MonteCarlo Program" ;-). >From the point of view of general computer go improvements, in other words, someone, anyone, making a really strong computer go program, the fact that GnuGo is a traditional style go program has kept the MCTS programs honest. Unfortunately traditional style programs don't scale so well. If the talented programmers here could put emotional attachments aside, it might be best to say GnuGo is now done, and to spend their efforts on another open source program like Fuego [1]. Darren [1]: http://fuego.sourceforge.net/ -- Darren Cook, Software Researcher/Developer http://dcook.org/mlsn/ (English-Japanese-German-Chinese-Arabic open source dictionary/semantic network) http://dcook.org/work/ (About me and my work) http://dcook.org/blogs.html (My blogs and articles) _______________________________________________ gnugo-devel mailing list [email protected] http://lists.gnu.org/mailman/listinfo/gnugo-devel
