Closed omidmnz closed 6 years ago
Shouldn't be the case with recent Pachi versions. Which version / graphical interface are you using, and how are you setting up the handicap game ?
This is the output of pachi -version
:
Pachi version 12.00 (Jowa)
git 98a3988 (master)
x86-64 dcnn build, Jun 9 2018
I use Sabaki (the latest version, 0.34.1), and let it handle the handicap and Komi. These are the commands I have tested:
pachi -t 10 --no-dcnn -f book.dat threads=4,pondering=1
And the greedy version
pachi -t 10 --no-dcnn -f book.dat threads=8,pondering=1,maximize_score
Revisiting these, I realize maybe I am not giving it enough time?
Indeed, there's a bug in sabaki: It doesn't setup handicap games correctly so pachi resigns thinking it's an even game. I'll forward it to them so they can fix it. In the meantime you could try playing through gogui, it works fine with handicap games. Thanks for reporting.
Time setting is up to you, 10s per move should be fine. It'll be stronger if you give it more, depends how fast/strong you want it to be.
Since the Sabaki issue is closed with a fix, I will close this issue too.
This is true for Pachi in both greedy and normal mode, but not for the DCNN (which does not know when to resign at all). Resigning on a lost game is the desired behaviour, but not on a handicap game. Is it possible to workaround this?