I checked the log files and see nothing bizarre. I looked for sudden score changes or cases where the program is winning and suddenly loses.
I also looked for early search aborting and saw none of that. FatMan will abort the search is the memory pool runs low. There is a very good chance this is merely due to low sample size. Each player has played less than 50 games and a couple of freak losses in a small sample can make a large difference in your rating. You probably noticed that the graph for Mogo was wildly up and down just a few games ago. However I'm still going to look at the source code - I haven't studied FatMan in many months. FatMan has early exit, but even that is implemented in a scalable way. If the score is extremely negative or extremely positive it will stop searching and play a move, but only when it has searched at least 1/10 of the nodes (or time) it had intended to search. In the log files of this study that I have access to, this has not yet changed the expected result of the game. But it's not a feature that should affect it's scalability. - Don Don Dailey wrote: >> I wonder if fatman trend near 13 is an artefact or if the curve shows it >> has reached some limit in scalabitly. >> >> > It's rather odd. I'm checking the log file and then I will check the > source code to see if I have some artificial limits in there. > > - Don > > > >> Alain. >> >> _______________________________________________ >> computer-go mailing list >> [email protected] >> http://www.computer-go.org/mailman/listinfo/computer-go/ >> >> >> > _______________________________________________ > computer-go mailing list > [email protected] > http://www.computer-go.org/mailman/listinfo/computer-go/ > > _______________________________________________ computer-go mailing list [email protected] http://www.computer-go.org/mailman/listinfo/computer-go/
