What i meant was, for next move, try to run fuego twice, one with min playout 23 , the other 2500 min playout, and see if the chosen move ,and the rate between explored moves, changes.topazg wrote:
If we're talking about sufficient data points to improve play beyond chance, then I suspect 1 move won't tell us much
i propose to do it only for next move because maybe esmeralddemon as a life and no time to run all those experiments for our enjoyment
.Unfortunatly i don t have much time at home those days and compiling/running fuego at work might be a liiittle too much
or i ll try it myself.Very interesting thread anyway
I really wish i had some time to burn on that.
My previous job was on automated software translation base on statistical algos, it was really a blast, so if i have been able to work on translation without being a linguist, i hope i could work on a MC go engine without knowing how to play.
Unfortunatly i am not sure that go engine dev really pays up the bills ...
seems pretty much forced, and 
is solid, if a little slow. But I doubt white should play 
. It seems a bit too slow for the situation. Also I've noticed black often considers the slide at 
, it seems to be a large point to take.
, probably because in playouts those stones have enough aji to be useful. But in practice, I don't think Chew needs to make that capture, and it's hard to see what black can do to crack that moyo. Also, as mentioned before, Fuego still thinks white will descend with :W46: , but Chew said he would push up, which leaves more cutting points.