Lizzie help

[John Fairbairn]

I have an early Lizzie installed (easily) but someone suggested an upgrade to Lizzie 0.7.

I tried and apparently can't get it to work.

I double-clicked the jar file and the board loaded, and there is some functionality: I can click stones on, load a file, open the menu, etc.

But the AI analysis is missing, I get a box saying "Engine is loading" and the ReadMe file warns it can take a little while, while it is fine-tuning. But I have waited an hour and there is no sign of life.

There are (I believe) 2 network files (for lz and kata). They are both .gz zip files. There is also a file 15b_244_408k_q. All in the same directory.

Any tips, please.

[Gomoto]

(The first start it takes a very long time to initialize the engine settings, much longer than earlier versions. But an hour is too long probably.)

Did you try CPU and GPU versions? Or are you using the Mac/Linux version?

If it works correctly you do not have to make changes to the network files, it should work right out of the box.

[Javaness2]

With Lizzie 0.7 (CPU) I found that KataGo did not work, this may be expected for my CPU
I opened it, left it for 5 minutes, then re-opened it.
It worked.

[Tryss]

If you used the GPU version, there may be a driver issue. By your description, Lizzie work, but the engines are not.

In Lizzie, go to parameters > Engine, and check the box "Show logs". Then press E to make appear the GTP windows, and restart Lizzie : that will show you what the engine tell Lizzie, and if there's an error, it should show here

[hyperpape]

I ran into similar issues at one point, and ended up giving up: https://github.com/featurecat/lizzie/issues/399

[Farodin]

Are you using the Lizzie interface?

I have the same issue every time I start up Lizzie, where the Engine seems to be loading forever without Lizzie showing any signs of life. What works in my case is just to press the spacebar (which, if my memory serves me correctly, triggers the 'pondering' function) after having allowed Lizzie to load for a couple of seconds. If you're lucky, that might just be enough to make Lizzie spring to life (as she does in my case).

[John Tilley]

John - I just downloaded Lizzie 0.7 and it worked on my aging computer (Windows 7 64bit) using LeelaZero. It took about 2 minutes to get past "engine is loading" and I have a ten year old graphics card. (Radeon 5700). You might want to check the basics:

1 - You must have a 64bit version of Windows to run a 64bit application such as Lizzie 0.7. Do you have a 64bit version of Java installed? Is it version 1.8? You can enter "java -version" on the command line. I have "1.8.0_221 64bit server VM"

2 - If you have an older version of Java I suggest you manually uninstall it and then install the latest 64 bit version. I had problems with GoWrite a couple of years ago when my version of Java got updated and it led to all sorts of problems with several applications.

3 - Download the CPU version of Lizzie and install it - that avoids any problems with the graphics card (assuming you have one).

Installation - Just unzip the Lizzie distribution which is 146meg. Leave the GZ files in the folder as are - LeelaZ can read these compressed files directly.

If this works then download the GPU version and install it. The default that I had was to run LeelaZ as the engine. If this doesn't work - then you need to look at your graphics card and drivers.

4 - There are various utilites on the web which will give you a summary of your graphics card - does it support OpenCL etc etc.

HTH - John

[John Fairbairn]

Thank you all for tips so far. I have tried what I can but I don't seem any further forward.

First, I did download the gpu version first. I assumed this mean "works with a GUI interface" as opposed to cpu = works from the "command line." I'm obviously out of kilter with the gaming age, so I downloaded the cpu version. I got exactly the same effect.

But then I tried the checks mentioned here. Java seems fine. The engine log was not where it was said to be here but there were enough clues to find it eventually, and that's where I got the extra information, which means nothing to me but may to you experts.

There was nothing in the "gtp console" like that looked remotely like an error message. What I got was a lznetwork.gz> prompt which offered initially information on name, version, boardsize and komi.

After waiting a very long time (over 10 minutes) I got bored and started pressing buttons. What I found was that the gtp console would update and for evert press of the space-bar it would added lznetwork.gz> X name, where X was a sequential number. I got up to 165 on one run (yes, that's how bored I was!) but it had no effect on making the engine work. Shutting down and reloading had no discernible effect.

Another possible clue is that if I switch "engine" to katago, the gtp console responds by saying "katago v. 1.2" and when I try to switch back to lizzie, it takes a couple of second before declaring "quit". That seems to suggest something was going on behind the scenes, but I gather loading katago takes much, much longer.

The gtp console will also respond if I click the board (it gives "play" and the move coordinate) but I can't get the console to respond by any other way than that or the space-bar (="name"). Although the gtp console doesn't show it, though, other commands such as menu and "show cooridinates" do still work as expected.

My Sony machine (Windows 10) is certainly old, but fully updated, seems fast, and I have no compatibility issues elsewhere.


One last splurge before I give up?

[John Tilley]

John - Both the cpu and gpu versions have the same interface - ie a nice graphical one. The cpu version doesn't attempt to use the power of a graphics card, just the processor. The gpu version uses the graphics card - so you need the right driver and different graphics cards have different interfaces. The cpu version is in all probability easier to get to work on any given computer.

I tried to use KataGo on my system this morning - it just sits there with "engine is loading" for many minutes. So out of the box I can get Lizzie to work with LeelaZero but not Katago.

I can't offer any more ideas.

Sorry - John

[lightvector]

I tried to use KataGo on my system this morning - it just sits there with "engine is loading" for many minutes. So out of the box I can get Lizzie to work with LeelaZero but not Katago.

It's possible that KataGo has failed to load, but it's also possible that it's simply running a tuning process to compile itself and test parameters to work on your hardware, which it does on the first-time startup. On a top-level GPU, this process takes only 15s-30s or so, but I could imagine it taking longer on more casual hardware.

KataGo tries to make it plain that it's doing this tuning, by outputting a bunch of stuff to the command line as it's doing so showing progress in the various phases of the tuning, but unfortunately it's an open issue that Lizzie doesn't by default display this output, as noted by hyperpape above (https://github.com/featurecat/lizzie/issues/399), so there's no easy way for the user to tell what's going on.

So, try running the KataGo gtp command that Lizzie is running directly within a command line console, outside of Lizzie as described here https://github.com/featurecat/lizzie/is ... -539194820 . This should make it clear whether it is failing or whether it is tuning successfully and just taking a long time. The tuning only needs to happen once, on every subsequent startup it should be fine after that.

Edit: Also as you might see from that Github thread, if you're using something like Intel integrated graphics, it might be a bit hit-or-miss whether it actually works.

[Jujube]

I have a 1050ti and had to update my drivers before 0.7 would run. Not using Windows Update, but actually going on the AMD website and downloading and installing the latest drivers. Then it worked fine, got past the Engine Is Loading screen in 10 seconds using GPU mode.

[Tryss]

KataGo tries to make it plain that it's doing this tuning, by outputting a bunch of stuff to the command line as it's doing so showing progress in the various phases of the tuning, but unfortunately it's an open issue that Lizzie doesn't by default display this output, as noted by hyperpape above (https://github.com/featurecat/lizzie/issues/399), so there's no easy way for the user to tell what's going on.

Not by default, but you can make Lizzie show you the log, as I explained in my previous message. If you check the "Print Engine log" options in the options, it will display the same thing in the GTP console of Lizzie as what it would display on the terminal.

Edit : Visual tutorial

Lizzie Display log.png (1.32 MiB) Viewed 17082 times

[Knotwilg]

Adding in - to John's frustration I'm afraid - that on my machine Lizzie 0.7 works like a charm. Downloaded the CPU version. Unpacked it. Launched the jar file. Switching engines to Kata took a good minute or so. This lazy user has his machine offered and maintained by a professional organization - I guess that helps.

[John Fairbairn]

KataGo tries to make it plain that it's doing this tuning, by outputting a bunch of stuff to the command line as it's doing so showing progress in the various phases of the tuning,

I tried this and, while it didn't work, the information outputted may help someone:

Uncaught exception: OpenCL error at C:\Data\Data\Coding\Python\Katago\cpp\neuralnet\openclhelpers.cpp, func err, line 188, error CL_PLATFORM_NOT_FOUND_KHR

[Tryss]

This error tell us that OpenCL (drivers to use your graphical card for computation) is not available on your computer.

Could you give your complete configuration of your computer ?

Open the search bar (right click on the lower right on the windows icon > Search), then type Dxdiag, the icon is a Yellow X in a blue circle. Run this, it will list your current configuration. The "System" and "Display" tabs are what's usefull.