I've looped through all 'm'-positionsThe following way: For each postion I find if the best move with my evaluator, and find if my move is among the candidates in the list of moves. If it does not make the best move, I add the error to the total. If my evaluators move is not among the candidaes at all, I assign the same error as the worst move among the candidates.
For all positions in contact.bm, GNU backgammon will have an error of about 1125, (IIRC) Please report how your players make it. -Øystein 2012/2/12 Mark Higgins <[email protected]> > Does anyone have the average error stats for 0-ply gnubg on the contact > benchmarks? > > I see race & crashed results at Joseph's page here: > > http://homepages.ihug.co.nz/~peps/ngb/index-top.html > > but can't find the contact result anywhere. (Though I'd guess it's pretty > close to the crashed error, ie around 0.01ppg/move.) > > > > > On Feb 10, 2012, at 6:26 AM, Øystein Schønning-Johansen wrote: > > 'r' is the seed used for the rollout, I think >> > > Sound likely, since there is an 'r'-line for every rollout result. But > there is no code lines in perr.py to conferm it. I guess we can trust your > memory on that. > > 'o' is the cube rollout, and the numbers are the rollout values of the > outcome probability, > > -Øystein > > >
_______________________________________________ Bug-gnubg mailing list [email protected] https://lists.gnu.org/mailman/listinfo/bug-gnubg
