
Black on move: Ron played 14-20 and eventually lost the game. BoomstraDam suggests 13-18 with a very small disadvantage. Other suggestions?
I would have been happy to compare Damy and Kingrow on such problem but it appears very difficult because Damy and Kingsrow do not use the same algorithm (MTD(f) vs MTD(f)-best).Ed Gilbert wrote:Gerard,
The previous result was with the 9pc db. I tried it again using only 7 pieces (and fewer) and it sees database draw in about 30 seconds, at depth 21. I let it continue to depth 25 and at each iteration it continued to show db draw.
-- Ed
Is there a documented FEN standard for draughts? I have not seen one. I use the same format as Martin Fierz's CheckerBoard program because that is an informal standard due to its popularity.wellnesswrotter wrote:Question about the FEN notation.
You keep putting a point after the FENstring.
But is that protocol? Not according to the Wikipedia page.
I understand now what you mean by "db draw".Ed Gilbert wrote:Remember that a db draw score, as you well know, does not mean that the position is guaranteed to be a draw (as it does with a db win or db loss). The search score is a mixture of db scores and heuristic scores propagated from the leaf nodes, and so a db draw score means that anyplace a db draw was compared to a heuristic score the heuristic score was inferior and the db draw was propagated
Yes Ed, your are right it is not difficult. My intention was to write a special algorithm in order to search the real result of a position : win, loss or "clear demonstrated draw". The program run until the correct result is found or when the operator decide to stop manually the exploration.Ed Gilbert wrote:I understand what you mean about mtd-best and not being able to obtain an exact score. Here's a suggestion: why don't you add some control to your user interface that lets you select either mtd or mtd-best as the search algorithm? The difference is only a relatively small amount of code at the root level of the search. I think you could conditionally use either algorithm without too much difficulty. Then you could turn on the ability to get exact scores when you are doing position analysis where that info is useful, and keep the mtd-best for tournament games.