In a paper published a while ago, Remi Coulom showed that 64 MC trials
(i.e., just random, no tree) was a useful predictor of move quality.
In particular, Remi counted how often each point ended up in possession
of the side to move. He then measured the probability of being the best
move as a
Hi Brian!
In my tests with Valkyria I have something like a 4-5% improvement in
winrate against gnugo using ownership. But I think you need to be much
more careful in how you test these things.
Testing on CGOS is a no-no for me, because the opposition changes from
hour to hour, so unless
On Jun 5, 2009, at 6:39 AM, Brian Sheppard wrote:
In a paper published a while ago, Remi Coulom showed that 64 MC trials
(i.e., just random, no tree) was a useful predictor of move quality.
In particular, Remi counted how often each point ended up in
possession
of the side to move.
Which
When I complete the new server, I hope that it will be easier to collect
larger samples of games. I think this will help the situation a little.
There will be multiple time controls, but they will be in sync, so that your
program can always play in a shorter time control game without missing a
: Fri, 5 Jun 2009 9:39 am
Subject: [computer-go] Negative result on using MC as a predictor
In a paper published a while ago, Remi Coulom showed that 64 MC trials
(i.e., just random, no tree) was a useful predictor of move quality.
In particular, Remi counted how often each point ended up
Which paper was this?
Computing Elo Ratings of Move Patterns in the Game of Go
ICGA Journal, Vol. 30, No. 4. (December 2007), pp. 198-208.
http://remi.coulom.free.fr/Amsterdam2007/MMGoPatterns.pdf
___
computer-go mailing list
I've also tried a variety of ways to use point-ownership in
combination with RAVE. By no means was it an exhaustive study, but I
failed to find an intuitive way to improve play this way.
I didn't try enough to be able to come to hard conclusions, but at the
very least it didn't turn out to be
