Re: [Bug-gnubg] Some more code-related questions

[Thomas Hauk]

Thanks again for the responses, Jim.

Here is what I've distilled from our discussion. The following lines of 
code are what I think would be needed in order to get gnubg to perform a 
standard (gnubg)2-ply search on any given board, for a 1-pt match:

   cubeinfo gnu_ci = {1, -1, 0, 1, {0, 0}, 0, 0, 0, {1.0, 1.0, 1.0, 1.0}, 
VARIATION_STANDARD};
   evalcontext gnu_ec = {FALSE, 0, 2, 0, 0};
   if(FindBestMove(gnu_move, die1, die2, gnu_board, &gnu_ci, &gnu_ec, 
defaultFilters) < 0) {
      printf("Cannot move\n");
   } else {
      printf("gnubg choses '%s'\n",FormatMove(temp_str, gnu_board, 
gnu_move));
   }

(Where die1 and die2 are the two dice values, and gnuboard is the 
arbitrary position)


Is this correct? I want gnubg to producing the best-quality search 
possible for the given ply setting ("grandmaster"?).


Also, what kind of time controls does gnubg have? I think Jorn mentioned 
to me that the standard Control-C interrupt can be used to stop the search 
routine if the user desires. I just tried that with the gui myself, but 
the problem is that while search seems to be stopped, a move isn't chosen. 
(I will want to be adding a way to constrain the time used per move later 
on).

-- 
Some people, when confronted with a problem, think "I know, I'll use 
regular expressions."  Now they have two problems.
  --Jamie Zawinski, in comp.lang.emacs