support for the next branch?
Closed this issue · 7 comments
Although LeelaWatcher can run with autogtp_next, no stones are displayed on the board as moves are generated.
looks like the next branch changed the output format so one needs to change the pattern matchings in AutoGtpOutputParser.java ...
Yes, I am seeing this when using autogtp 11 too. I'll have a look at fixing AutoGtpOutputParser if I can figure out how things changed.
I think I found the change in the leela-zero source that broke LeelaWatcher.
On 12/9 Marco Calignana made a change to autogtp/Game.cpp to improve the move output.
Instead of writing " ()" for each move, it now writes
" ( <moveCoords)" for each move.
If I fix this, I assume that we need to bump the version and then say something like 1.0.3 will only work for leela-zero gtp version 11.0 and above, while 1.0.2 is for previous versions.
Oh never mind, I see that there is already an outstanding pull request for this problem submitted 9 days ago. Hope it can be merged soon.
Will try to get to it soon, sorry for the delay I was on vacation, and of course work piles up before and after vacation...
This is also a dupe of #19.
fixed in release 1.1.0