Hi Remi,
Thanks for the reply. There are so many parameters to tune and
heuristics to try, and having two types of search (playouts and the
MCTS) doubles the number of knobs! (More than doubles, as there is the
interaction to consider too.)
I did not try your position. But understanding seki is
Darren Cook wrote:
Was there a reason in not using criticality as a guide in playouts too?
Or just lack of time to experiment with it?
No particular reason, except maybe that it would be difficult to do, and
I do not really know how to implement it.
I am convinced that the idea of
Hi,
I have just come back from a trip to Japan. I was invited to give
presentation at the JFFoS Symposium and the UEC. You can now find slides
of my presentations on my web page:
The Monte-Carlo Revolution in Go
http://remi.coulom.free.fr/JFFoS/JFFoS.pdf
(Nothing new here. A simple
Original-Nachricht
Datum: Sun, 01 Feb 2009 11:01:12 +0100
Von: Rémi Coulom remi.cou...@univ-lille3.fr
An: computer-go computer-go@computer-go.org
Betreff: [computer-go] JFFoS + Criticality Heuristic + Parameter Optimization
Hi,
I have just come back from a trip to Japan. I
Isaac Deutsch wrote:
Hi,
The criticality stuff looks really interesting. Do you apply it with the
offline knowledge, or as a RAVE prior value, or otherwise? It looks like
you precalculate (before the MTCS) the ownership + criticality map, maybe
it can be extracted from playouts in the MTCS as
Darren Cook wrote:
I don't precalculate before MCTS. Criticality, like point owner, is
re-calculated for each node of the tree, as it grows. It is computed
from MCTS playouts.
More precisely, search at a node starts without MC features. Move gammas
are all computed with static features only.
