I'm assuming small boards. For big boards it's not practical to have a database style book of course.
You definitely must take into considerations board orientations. I suggest using a database where the position is hashed. You can do your own or you can use a lite sql database such as sqlite which is easy to work with. Use a good 64 bit hash of the positions as the key, and determine it some canonical way. If you use a sql database of some sort, you can be pretty flexible and I suggest that you put in flags to identify the source of the moves. For instance you could place moves in the database based on human games, strong computer games, self generated games, hand edited books moves and probably others I didn't think about. If you can specify how the move got into the book you have a great deal of choice about which class of move you use under which conditions. The flags should not be mutually exclusive. Another thing you may want is a quality indicator so that you can specify some moves as tournament quality versus other moves that just provide variety. Even if the book is compiled into your program without using a database, I suggest that it is based on an external sql databse that you can use for editing and developlment. That's probably how I would do it so that the book did not have to be dragged around with the program. Unless of course the book was really large. - Don On Wed, Jun 17, 2009 at 7:44 AM, Willemien <wilem...@googlemail.com> wrote: > I was puzzeling what is the best way to organise an opening book? > > i am writing a program to be very strong on 7x7 go program (as > prelimary for writing a very strong 9x9 program ) and am wondering > what is the best structure for an opening book. > > Where i am at the moment is: > > There are about 4 fundamentally different ways to structure it > > 1 a position -> move collection (if the position is such make that move) > 2 a position value collection (this position is good, that position is > bad for the colur who is on the move) > 3 a professional game collection (let the program just play like the > pro's) > 4 a game tree (game with lots of variations) > > > all have there advantages and disadvantages. > > 1 is close to what the program uses but is a long list. (difficult to > maintain?) > 2 same problem as 1 maybe even more extreme, but easy to use for the > program > > 3 are reasonably easy to find. (for standard sizes Godod ed) but has > many hiatus (what if > my opponent doesn't play like Go Seigen) > 4 is easy to use with go editors (Drago ed) but problems with > transpositionings ed. > > I would like to hear from others what kind of opening book they use > and why. and how they maintain it. > and if i am missing important things. > _______________________________________________ > computer-go mailing list > computer-go@computer-go.org > http://www.computer-go.org/mailman/listinfo/computer-go/ >
_______________________________________________ computer-go mailing list computer-go@computer-go.org http://www.computer-go.org/mailman/listinfo/computer-go/
