Hello,
> On 11/30/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > To give an idea of the scale (at least for MoGo), 70k simulations/move > > (with the best parameters) against gnugo 3.6/level 8 gives 89% in 9x9, > > 68% in 13x13, 32% in 19x19. > > This is still not assessment of scalability. Each of those 70k > simulations takes longer for larger board sizes. Yes of course. But also gnugo takes more time in larger board size. Futhermore in 19x19 games you have more time to play. Anyway gnugo always takes far less time that MoGo, but when allowing more time to gnugo it does not improve so well. We are not talking about blitz are we? Of course in blitz games, gnugo is unbeatable. I think what is important is the level you reach with a reasonable game time. > Do you have these > numbers for x seconds per move? At the very beginning we were experimenting using seconds/move. They are some issues doing that. First it depends on the speed of your computer, so difficult to compare when doing experiments in different computers. Second it depends on the optimisation. It is far simpler to come up with an idea, implement it "badly" (without optimisation), see if it improves with the same nb of simulations, and then think about optimisation (if possible). Of course this holds only if after optimisation the evaluation takes a time comparable without the idea. On a P4 3.0Ghz mono processor, the number of evaluations per seconds is in the order of 4500/s in 9x9, 2500 in 13x13 and 1100 in 19x19. > Or mirroring Gnu-Go's thinking time? No, gnugo plays far faster. I already discuss that above. Sylvain _______________________________________________ computer-go mailing list computer-go@computer-go.org http://www.computer-go.org/mailman/listinfo/computer-go/
