q5go-2.1.3: Autoplay and some other minor updates

[And]

bernds My gratitude to you is as great as Fuji!!!

[bernds]

Actually I didn't really consider saving and loading such SGF files - there's a comment in the source that suggests I saw inconsistencies in other programs and decided to disallow anything > 25. So that's a gap in version 1.1 - you can still play these against the computer.

[And]

maybe saving and loading sgf files implement as on KGS and in MultiGo? http://www.ruijiang.com/multigo/
37×37 http://files.gokgs.com/games/2012/7/22/ ... link38.sgf

EDIT: I checked, MultiGo loads without errors sgf(37x37) from KGS, and vice versa (CGoban loads without errors sgf from MultiGo).
Lizzie and Leela 0.4.6 uses the same format sgf for boards over 25x25 (I checked on 29x29)

[And]

q5go-1.1 saves sgf up to 29x29, using in addition "{", "|", "}". but does not load. I found a temporary solution - in sgf in a text editor, you need to replace these characters with "A", "B", "C". The resulting sgf opens without errors in MultiGo, CGoban, and Sabaki!

[lightvector]

Actually I didn't really consider saving and loading such SGF files - there's a comment in the source that suggests I saw inconsistencies in other programs and decided to disallow anything > 25. So that's a gap in version 1.1 - you can still play these against the computer.

In FF[4], the latest version of the SGF standard (since 2006?), it seems to be explicitly documented how to continue beyond size 26 (sgf does not skip the "i"), all the way up to board size 52:
https://www.red-bean.com/sgf/go.html#types

So perhaps the inconsistencies you saw were either from other programs not conforming to the standard, or from choosing to implement a pre-FF[4] version of the standard? I do think there are quite a few SGF parsers that don't quite conform to the standard though which is maybe what you noticed... Go software in the wild is a bit of a mess sometimes. It's hard to get all the corners exactly right, good chance my code in KataGo doesn't either.

[bernds]

Actually I didn't really consider saving and loading such SGF files - there's a comment in the source that suggests I saw inconsistencies in other programs and decided to disallow anything > 25. So that's a gap in version 1.1 - you can still play these against the computer.

In FF[4], the latest version of the SGF standard (since 2006?), it seems to be explicitly documented how to continue beyond size 26 (sgf does not skip the "i"), all the way up to board size 52:
https://www.red-bean.com/sgf/go.html#types

So perhaps the inconsistencies you saw were either from other programs not conforming to the standard, or from choosing to implement a pre-FF[4] version of the standard? I do think there are quite a few SGF parsers that don't quite conform to the standard though which is maybe what you noticed... Go software in the wild is a bit of a mess sometimes. It's hard to get all the corners exactly right, good chance my code in KataGo doesn't either.

I suspect the comment was very old, as the SGF loading code is derived from something I wrote ages ago. I've already fixed things to follow the FF[4] spec and will make new binaries next time I reboot into Windows.

[And]

please add "engine match" to the "computer game" tab (autosave - games in sgf), for example like this:

[bernds]

please add "engine match" to the "computer game" tab (autosave - games in sgf), for example like this:

Do you mean play between two engines? That's already there, but it's not available from the greeter window. The client window has the full set of menus and options; the greeter has a message to that effect in version 1.1.

[And]

the game between the two engines works great, thanks! I'm about a series of two engine games or a computer tournament. for example, two engines play 50 games and the results are saved in sgf. that is, you can leave the computer at night, and then see the games

[bernds]

the game between the two engines works great, thanks! I'm about a series of two engine games or a computer tournament. for example, two engines play 50 games and the results are saved in sgf. that is, you can leave the computer at night, and then see the games

I don't understand what you are asking. There already is a "Number of games" field, which sounds like exactly what you want?

[And]

a field that already exists, for playing variants for one game, I tried. a new game does not start, but a new continuation is played out with a certain move. it is different. Or can I somehow start the match?

number of games: 5 (view screenshot)
these are not 5 different games. and would like to sgf these games
match engines can be made in GoGui (gogui-twogtp) or SmartGo, but they do not have a size of 29x29

[bernds]

a field that already exists, for playing variants for one game, I tried. a new game does not start, but a new continuation is played out with a certain move. it is different. Or can I somehow start the match?

number of games: 5

These are all new games. Some of them start with the same moves, so you see them as branching off at various points. Once play completes, there should be a match summary in the root node.

[And]

Thank you so much! I looked from the other side and it is interesting! wonderful program !!!

[bernds]

I like having the results of an entire match in a single SGF file. It allows following the match in one window while it's running. But I've added a new feature to save all individual variations into their own files (in the File menu). That might get improved a little in the future to interact better with game results from an engine match.

For now, there's no new release, but thanks to a contribution from Fan Yang there are now Github actions which automatically build the repository on each push. Please note that I don't control the build environment for this, it's all provided by Github, and in theory there are trust and/or security issues with that. In practice, most people have no problem with it. If you decide you're OK with this and wish to try them out, the most up-to-date build artifacts as of now are

Mac build
Windows build

Careful with the Windows archive, it doesn't extract into a new directory but just splats all the files into the destination path, so make sure you create an empty directory first. I'm trying to figure out how to fix that in the scripts but no luck so far.

In the future, you can look for and click on a green checkmark next to the "Latest commit" message on the github home page and find the most recent builds from there (or from the "Actions" tab).

[And]

perfectly! SGF works up to 52x52!
(in sidebar, some moves are not displayed correctly (for example, AC 28 - ] 28))