josekifix

[GD-fix]

Offer: to add open code with josekifix support directly in Pachi code or remove from version printout "(joseki fixes disabled)".

Thanks in advance.

[GD-fix]

Are these models work in Pachi without installed KataGo?

[lemonsqueeze]

Hi,
No, you need KataGo to use them.
Next release should have KataGo included so it'll be much easier to setup =)

[GD-fix]

Hi!

Thanks. Will wait for the next version...

[lemonsqueeze]

Pachi 12.86 pre-release is out =)

[GD-fix]

Thanks!

But I didn't understand: for using with --modern-joseki I must download additionally the KataGo network?
If yes, may it be from here?

[lemonsqueeze]

I'd suggest using Pachi 12.86 release which has everything needed.

If you are building it yourself then you need katago and katago model for this to work. Follow instructions on the Install page and Makefile, or extract them from the binary release either way should work.

[GD-fix]

Thanks!

No, I'll use the binary release.
It doesn't work with KataGo networks from mentioned link. Am I right?

[lemonsqueeze]

The KataGo networks in binary releases are the same as in the link above.
If you want to use another network you can use --kata-model option.

[GD-fix]

So, the kata1-b28c512nbt-* networks will work with --kata-model option. Did I get it right?

[lemonsqueeze]

Should work but probably will be slower, these networks are bigger.
You might have to adjust number of playouts in katago.cfg.

[GD-fix]

Thanks.
I'm using the time on move...

[GD-fix]

With the non-default "--modern-joseki" parameter Pachi plays really stronger (details), but "allowResignation = true" in the katago configuration may lead to game termination with error:

pachi: move.c:83: str2coord_for: Assertion `valid_coord_for(str, size)' failed.

May be pachi must give katago_cpu "allowResignation = false" parameter that overrides the katago configuration?

With the default katago.cfg, "-t 120" and "--kata-model kata1-b28c512nbt-..." there was appeared output on the GTP shell like this one:
*** LOST ON TIME internally! (-38.86, spent 158.86s on last move)
May be pachi doesn't give the right GTP command that tells katago_cpu that it is playing under a clock?

External KataGo engine doesn't load:

external engine: malformed answer: '
'

[lemonsqueeze]

Hi,
Thanks for the feedback.

Yes, katago.cfg must have allowResignation = false to prevent issues like this.
Are you using katago.cfg that comes with Pachi releases ? It should have it already.
If you're using another katago.cfg make sure to copy settings from Pachi's katago.cfg

For the second issue, looks like the problem is that Katago's thinking time is determined only by katago.cfg, there is no communication of time settings between Pachi and Katago. If you want 120s per move for both Pachi and Katago try something like this :

• Pachi: pachi -t 120
• katago.cfg: maxTime = 100 (comment out maxPlayouts and maxVisits if present)
  (use a bit less for Katago so Pachi doesn't time out)

[GD-fix]

Hi!

I'm offering of configuration file overriding parameter adding just for end user convenience and freedom of configuration using (in particular if external KataGo engine loading will work)...

In KataGo configuration file comment is written:

# For all of "maxVisits", "maxPlayouts", "maxTime", search will still try to follow GTP time controls and may make a move
# faster than the specified max if GTP tells it that it is playing under a clock as well in the current game.

Are You sure, that Pachi "tells that it is playing under a clock" KataGo in right way?
Of course, I used appropriate time on move (see link below for details), but when using katago.cfg that comes with Pachi releases and fixed time on move Pachi parameter it may lead to this warning (especially with non-default "kata-model"), and I direct your attention to this just for end user... (see above).

I offer to add a "--modern-joseki" parameter as default: with it Pachi plays really stronger (details).