I have a new PC, bought for the purpose of running KataGo.
The CPU is an i7-14700K and the GPU is a GeForce RTX 4060.
Once again, my son built the PC and we installed Debian 12 together.
(I was previously stuck on Debian 11.) Video output goes
through the GPU and everything seems to be working.

The current build instructions are very different to what I used before. The advice
(forgotten where it is) was to build leela-zero, then lizzie and finally KataGo,
so I tried that.

I believe all the required Debian packages were installed.

The attempt to build leela-zero resulted in various incomprehensible errors, of
which the last is shown below. A leelaz binary is left behind, but cannot be
tested.

The attempt to build lizzie got nowhere. The current instructions are

It is unclear in which directory to issue the mvn (Maven) command. It is also
unclear whether 'package' is to be interpreted literally or is a place-holder for
an input or output name. Running the command as it stands caused Maven to
complain about a missing BOM (Bill of Materials?) and give up.

I haven't tried to build KataGo. I may now be too old and sick to succeed in
the installation. I can no longer play over a real board, but do not seem to
have lost any strength playing online.

Reverting to Debian 11 is not an option because it predates the introduction of
the GeForce 4060 and is unlikely to have the correct drivers.

I retried importing the binaries from Debian 11 for lizzie, leela-zero and KataGo.
Lizzie runs and can load Leela-zero, but the engine fails to analyse anything.
KataGo does not run. This is no surprise because the old engines probably embed GPU
libraries that do not work for the 4060.

I then built build KataGo afresh using these instructions and
placed it under lizzie/target.


This worked, and the analysis now runs 3 times faster than on the old PC, without
any explicit optimisation. Eventually the number of threads was doubled
in setting numSearchThreads = 24 in file gtp_custom.cfg.

EDITED TWICE TO REFLECT "IMPORT OLD BINARIES".

EDITED AGAIN FOR FUTURE REFERENCE AND TYPOS. 22 June 2024

Issuing the following command watch -n 1 nvidia-smi
generates a display like the following.

The aim is to monitor the temperature of the GPU. In practice, it does not
exceed 60 Celsius when analysing at 100% GPU loadm which is good.

The bottom right corner shows memory used in the GPU's other role of driving the
display. When first running KataGo under lizzie, some memory was also taken by
leelaz, which is not doing anything. It may not matter much, but
killing that instance of leelaz removed it from the list. A better solution
is to use the Settings/Engine menu item in lizzie to blank the engine
parameters for leelaz in lizzie/target/config.txt so that leelaz never starts.

I used not


I don't need the super strength, and the b28 model runs much slower on my PC.
Whether b28 at 3000 visits would be stronger than b18 at 7000 is not a question
I can answer. I always used 7000 visits with the old installation.

If you're wedded to leela-zero and lizzie I can't help you. If you're just interested in getting some AI going, I had fairly quick success with katrain (https://github.com/sanderland/katrain). I ended up having to build katago from source on an Ubuntu system, but that was without difficulty.

Good luck!

There are binaries available on github for KataGo but maybe not Leela zero. Maybe you should try those binaries?

The error that you have with compiling Leela zero is really something simple. You are compiling with a newer (or different) compiler than the code was tested with. These are actually warnings but the build is configured to treat them as errors. You could try to disable this feature of triggering an error if the compiler finds a warning.

Normally later compiler options override earlier ones which means it can be tricky to disable this behavior. New versions of CMake have --compile-no-warning-as-error flag to do just that, but this might not have any effect if the project isn't set up to respect this flag (for example it could predate the addition of the flag to CMake).

Btw you appear to be building the tests, maybe you won't have this error if you only build the release target?

Thanks for the heads up. I should have realised that Lizzie is now abandonware.

The reason for keeping the same software is that the data from analysis sessions
is saved and passed to extensive scripts written by me that reformat the numbers
into human-readable comments for insertion into the SGF file. The data is probably
written directly by KataGo, but things might be different with another GUI in place.

As a check, I analysed some old SGF files with the old and new KataGo, but
with the old Lizzie and the same network in both cases. Evaluations differ
by a few points in some cases, but are broadly compatible. I can now continue with
GPU optimisation and newer networks, while always having a working setup available.

Disable Werror in /gtest/googletest/cmake/internal_utils.cmake




Perhaps jar files are created in "target" directory by maven's default setting.