H.G.Muller wrote:Strange that you have to specify this duringthe making of the book, as it throws away information (on the move frequencies), and does not substitute anything in its place.
It does substitute something : an equal frequency.
You do not take into account the fact that the most advanced way of making PG books is to build several books that you merge in a specific order.
For example if I just wish my engine to play either 1.d4 or 1.c4 as white and nothing else, I can make a one-ply long book with just two game fragments (first game is 1.e4 and second one 1.d4) with options "uniform" and "white-only". Then i use the book-merge function to combine this one with a second more usual book.
How could you replicate the way my engine will play with this combined book through an option that would be activated only during play?
H.G.Muller wrote:This option would be much more logical on using the book. Then you can keep the information on the move weights in the book, but simply ignore it when picking a move.
... but you have no way to get the precise choice of moves I get in my little example (forced e4 or d4 then moves according to PG heuristics on a large database).
In fact the precise goal of adding "book-merge", "only-white/only-black" and "book-merge" to the book making features of Polyglot was the possibility to combine fixed-lines with the broader knowledge coming from large databases in view of preparing Fruit competition books at summer 2005.
Don't forget that we had no way to change the weights "manually" once the book had been built at the time (this came much later with P George's added features in SCID)
This mechanism was elaborated by Fabien after quite a series of mail exchanges with myself.
Marc