Re: [computer-go] Fuego technical report
I found an error in the documentation: === void GoUctCommands::CmdParamPlayer ( GtpCommand cmd ) === Get and set GoUctPlayer parameters. This command is compatible with the GoGui analyze command type param. Parameters: auto_param See GoUctPlayer::AutoParam early_pass See GoUctPlayer::EarlyPass ignore_clock See GoUctPlayer::IgnoreClock reuse_subtree See GoUctPlayer::ReuseSubtree use_root_filter See GoUctPlayer::UseRootFilter max_games See GoUctPlayer::MaxGames resign_min_games See GoUctPlayer::ResignMinGames resign_threshold See GoUctPlayer::ResignThreshold search_mode playout|uct|one_ply See GoUctPlayer::SearchMode === The last line should read: search_mode playout_policy|uct|one_ply See GoUctPlayer::SearchMode Martin Mueller wrote: Our technical report describing the Fuego framework is now available on http://www.cs.ualberta.ca/research/techreports/2009/TR09-08.php I will probably make at least one more revision, so all feedback and suggestions are welcome. Thank you Martin ___ computer-go mailing list computer-go@computer-go.org http://www.computer-go.org/mailman/listinfo/computer-go/ ___ computer-go mailing list computer-go@computer-go.org http://www.computer-go.org/mailman/listinfo/computer-go/
Re: [computer-go] Fuego technical report
How do you set the number of threads that you want Fuego to use? Does the windows version support multiple threads? Michael Williams wrote: Very nice. I do have one suggestion for Fuego. Make use of the ability to filter certain root moves out of the UCT tree to remove symmetrically equivalent moves. Or if it is not cost-prohibitive, throughout the tree. Martin Mueller wrote: Our technical report describing the Fuego framework is now available on http://www.cs.ualberta.ca/research/techreports/2009/TR09-08.php I will probably make at least one more revision, so all feedback and suggestions are welcome. Thank you Martin ___ computer-go mailing list computer-go@computer-go.org http://www.computer-go.org/mailman/listinfo/computer-go/
Re: [computer-go] Fuego technical report
Martin Mueller wrote: Our technical report describing the Fuego framework is now available on http://www.cs.ualberta.ca/research/techreports/2009/TR09-08.php I will probably make at least one more revision, so all feedback and suggestions are welcome. On page 2, the report says | The reference MCTS implementation by Dailey [6] provides a very useful | starting point, but is far from a competitive system. But reference [6] is to a description of a non-tree-search program. -M- ___ computer-go mailing list computer-go@computer-go.org http://www.computer-go.org/mailman/listinfo/computer-go/
Re: [computer-go] Fuego technical report
Very nice. I do have one suggestion for Fuego. Make use of the ability to filter certain root moves out of the UCT tree to remove symmetrically equivalent moves. Or if it is not cost-prohibitive, throughout the tree. Martin Mueller wrote: Our technical report describing the Fuego framework is now available on http://www.cs.ualberta.ca/research/techreports/2009/TR09-08.php I will probably make at least one more revision, so all feedback and suggestions are welcome. Thank you Martin ___ computer-go mailing list computer-go@computer-go.org http://www.computer-go.org/mailman/listinfo/computer-go/
[computer-go] Fuego technical report
Our technical report describing the Fuego framework is now available on http://www.cs.ualberta.ca/research/techreports/2009/TR09-08.php I will probably make at least one more revision, so all feedback and suggestions are welcome. Thank you Martin ___ computer-go mailing list computer-go@computer-go.org http://www.computer-go.org/mailman/listinfo/computer-go/
Re: [computer-go] Fuego technical report
Overall, it's a good read. Nitpicks: • The scalability graphs need to be clearer. Maybe add a caption or change the single-threaded label? I looked at the graphs first and took a bit to figure out why single-threaded outperformed all else. • The RAVE section wasn't all too clear. I think it tried to explain too much or tried too hard to avoid math. • The scalability graphs aren't very informative once the win rate gets too high. It'd be better if the reference had something like four seconds per move instead of one • The placement of graphs at the end felt awkward, but it may be the best place for them since I believe the paper's goal is ease of reading. Maybe make the references to the graphs less explicit in the text? Sent from my iPhone On May 4, 2009, at 1:54 PM, Martin Mueller mmuel...@cs.ualberta.ca wrote: Our technical report describing the Fuego framework is now available on http://www.cs.ualberta.ca/research/techreports/2009/TR09-08.php I will probably make at least one more revision, so all feedback and suggestions are welcome. Thank you Martin ___ computer-go mailing list computer-go@computer-go.org http://www.computer-go.org/mailman/listinfo/computer-go/ ___ computer-go mailing list computer-go@computer-go.org http://www.computer-go.org/mailman/listinfo/computer-go/
