- Lizzie-improvements
- Lizzie - Leela Zero Interface
- Running a release
- Changes in the initial release (v1.0)
- Changes in v1.1
- Fixed initial placement for handicap games
- Fix obsolete "Leela Zero" for the default player name
- Fixed a bug where the win rate graph would cross the board
- Fix saveBackRouting skipping nodes
- Fix: "Pondering on/off" was not updated by Analyze button
- Fix (scoreMean & scoreStdev)
- Option to opaquely paint grayscale territory prediction on board
- Changes in v1.2
- Changes in v1.3
- ecord startup log for #756 even when printCommunication is not set #759
- Show dialog for #756 when engine ended unintentionally
- Show "Engine is down." in trouble instead of "Engine is loading..."
- Show GTP console when engine ended unintentionally
- Import komi fix for Fox SGF from KaTrain (ref. #755)
- Fix #752 (deadlock by Fox SGF)
- Changes in v1.4
- Changes in v1.4.1
- Changes in v1.5
- Changes in v1.6
- Display existing .sgf file when savingfile
- Allows reading of uppercase .SGF and .GIB files
- Display an arbitrary engine name instead of the weight file name
- Toggle large winrate graph by mouse click of center button
- Restore all checks in View > Panel at startup
- overflow of pondering message in Panel UI
- Fix wrong "Engine is loading..."
- Fix obsolete "Pondering on" by Analyze > Toggle analyze
- variation tree was not updated by click to redo in panel UI
- Display the analysis result when the file is loaded
- Changes in v1.7
- Changes in v1.8
- Leela 0.11.0 on Lizzie 0.7.4
- Accept only numbers as blunder thresholds
- Make the threshold 0.0 usable for the blunder color of "normal" moves
- Fix(slow play/undo/redo)
- Fix #805(The ">>" doesn't work properly)
- Fix overflow of variation tree with largeSubBoard in normal UI
- Win rate graph related
- Fix: Remove wrong-sized ownership marks
- Fix: Up arrow key does not work just after click on a suggested move …
- Changes in v1.9
- Changes in v2.0
- Changes in v2.1
- Changes in v2.2
- Changes in v2.3
- Changes in v2.4
- Apply change diagram confirmation function to normal mode
- Aply "Add as branch" to normal mode
- A function to display the start number in advance when checking the change diagram
- About inputting engine commands
- Fixed an issue that suddenly warped past nodes in panel UI mode
- Bug that the move number "1" is not displayed
- Fixed variation tree drawing
- Fixed a bug where the rightmost change is not visible in the variation tree
日本語での説明は、こちらのリンク先をご覧ください→ https://ameblo.jp/hope366/entry-12653845300.html
Lizzie is a graphical interface allowing the user to analyze games in
real time using Leela Zero. You
need Java 8 or higher to run this program.
See the Wiki for learning more.
Just follow the instructions in the provided readme in the release.
The first run may take a while because Leela Zero needs to set up the
OpenCL tunings. Just hang tight, and wait for it to finish, then you
will see Leela Zero's analysis displayed on the board. Feel free to supply
your own tunings, as this will speed up the process. Do this by copying
any leelaz_opencl_tuning file you have into the directory.
First, you will need to have a version of Leela Zero that continually outputs pondering information. You can get this from one of the Lizzie releases or build it yourself; just compile from the next branch of Leela Zero (see http://github.com/gcp/leela-zero/tree/next for more details).
$ git clone --recursive --branch next http://github.com/gcp/leela-zero.git
The simplest way to build Lizzie is to use Maven.
To build the code and package it:
$ mvn package
$ java -jar "target/lizzie-0.7-shaded.jar"
(or whatever the current version of the shaded jar file is in
target/).
After you run this command you should see a GUI start. Lizzie will also start a Leela Zero
process that it will communicate with. You can configure the location of Leela Zero from the
config.txt file from the folder you started the java command. If Lizzie is unable to start
Leela Zero it will display an error and you can fiddle with the config.txt file
until you get all the paths correct.
Lizzie will provide multitude of options to load and save SGF files, run an auto analysis and configure the board. To see all the options just hold down the key x (yes, just press and hold the letter x) and you will see all the commands listed in the GUI.
When studying with katago in lizzie, there was a problem in drawing the graph when the winning rate display method was Lcb.If the score difference becomes extremely large, the graph will not be drawn correctly and the vertical movement will be repeated violently.This has been improved in v1.0. This screenshot shows a 5 stone handicap game setup. White 2, 4, 6, 8 are passes.
With LeelaZero, for example, Q3 is searched 10 times and the average win rate is 43.16%. LCB at this time is 40.86%.
Q3 -> 10 (V: 43.16%) (LCB: 40.86%)
In 10 searches, the winning rate of 43.16% shifts 2.3% (43.16-40.86) up and down, In other words, the true win rate is in the range below.
40.86% <= 43.16% <= 45.46%
This smaller one is the LCB, and as the number of searches increases, the deviation becomes smaller and the LCB approaches 43.16%.Generally, MCTS starts the one with the largest number of searches in Root, but Leela Zero uses the one with the largest LCB.I'm supposed to choose. This was about +70 Elo stronger.
This screenshot is the second station of the 5th match of Alpha Go and Isedle 9th dan.The screenshot left is a real-time analysis, and the screenshot right is a sgf file saved in panel UI mode and loaded.The screenshot left showing the white win rate of 34.3% is correct and the screenshot right shows the previous number.This bug has been fixed.
Although the numerical value showing the disparity information is displayed in the upper center of the winning percentage bar, there was a bug that the numerical value here was always 0 when the pre-analyzed sgf file was read and moved with pondering off.In v1.0 this confusing display has been removed.
Put the jar file and the sound folder in the lizzie folder.When you start lizzie, an item called Settings → Play Sound has been added, so you can switch on/off the start sound here.You can also switch by ""play-sound": true," in config.txt.
Tuning is performed only the first time when the OpenCL version of katago is started with lizzie, so it may take a considerable time depending on the performance of the computer.So some people may give up thinking it is a bug or freeze.With this fix, the GTP console is displayed only at the first startup, and you can see that the tuning work is being performed internally.To verify, delete the KataGoData folder in the lizzie or katago folder and then launch the OpenCL version of katago with lizzie.
In the official release version, "Leela Zero is loading" will continue to be displayed in the lower left until the analysis starts, regardless of the engine type.The modified version will display "Loading engine".
In v1.0, the starry sky background is applied by default, but the user can apply any image.For the background image, put your favorite image in the yasnaya folder in the thema folder of the Lizzie folder, set the upper menu to yasnaya in the theme tab from the settings of the upper menu, and you can make it your favorite image with the path of the background image below it. I will. (It will be reflected when Lizzie is restarted after the change) We also recommend 1920x1080 as the size of the image file used. If the file size is small, it may not be displayed properly.
In the official release version, komi is set to 7.5 points, but it has been changed to apply 6.5 points at startup.This is convenient when using katago to consider Japanese rules and Korean rules. leelazero has no effect because it does not support variable komi.
In KataGo's handicap game, the initial placement was randomly determined, but it has been changed to the official placement.
When playing a new game with KataGo, "Leela Zero" was displayed in the game info dialog box and the player name at the bottom of the board, but it has been changed to "AI".
When loading a pre-analyzed sgf file and moving it from the beginning with pondering off, if the automatic width adjustment of the winning percentage graph is enabled, the graph appears to cross the main board greatly.This bug has been fixed in v1.1.
See the screenshot below. In the above screenshot, switch the engine from Katago to leelazero. It should be in the same phase, but the result will show the point of another previous branch, as in the screenshot below.Thus, if you have several branches, switching engines may show aspects of another previous branch. This bug has been fixed in v1.1.
When Pondering on is displayed, click the "Analysis" button on the toolbar to stop the search on the board. However, it does not update to "Pondering off" until you move the mouse cursor over the main board. In the modified version, "Pondering off" is displayed immediately after clicking the "Analysis" button.
There are three items above the winning percentage graph: "mean", "stdev", and "Last move". In real-time analysis, all three work normally, but when moved with the pondering off, "mean" and "stdev" are fixed at the final numerical values and do not work properly.In v1.1, these two non-functioning items were hidden when moving with pondering off.
About the lower menu "Kata Estimate", added the option to display with opaque white to black paint.To switch, go to View → KataGo Settings → Trend Information → Brend with board. The shortcut key is "Shift-Period". The changes will be reflected when you turn on Pondering on.
Some FOX GO game records contain many explanations and branches. This is often seen in official competitions between professionals. If you save this and load it with lizzie, lizzie may freeze. This bug has been fixed in v1.2.
Previously, lizzie did not display any information if lizzie could not be started normally due to some flaw. With this fix, an error message will be displayed in a dialog box if the engine is improperly installed.
This is a fix for GONGJE (komi) when loading a GIB format file, but the details are unknown and are currently under investigation.
Lizzie can freeze in switchEngine if the engine does not close its pipe after the GTP command "quit" for some reason.I'm afraid this may occur when users write their scripts for cloud engines. This bug has been fixed in v1.2.
Details are unknown.See here.
The main reasons why lizzie does not start normally are that the engine command input is incorrect, the contents of the KataGo configuration file are incorrect, the weight file is incorrect, and so on. In such cases, lizzie will display in the Gtp console why it failed to start.
Displays an error message in a dialog box if the engine fails to start.
If the engine fails to start, the status display at the bottom left was previously displayed as "Loading engine ...", but it has been changed to "Engin is down".
With some of the above fixes, users can now easily identify the cause when lizzie fails to launch successfully.
For example, if you start lizzie without placing it in the weight file lizzie folder, it will look like the screenshot below.
The FOX GO SGF file may contain incorrect komi values. Fixed to be converted to the correct komi value and read when loaded with lizzie
When loading a FOX GO SGF file, lizzie may freeze. A simple fix was made in v1.2, but a more ideal fix was made in v1.3. See here for more information.
Lizzie-v0.7.4 had a bug where the winning percentage and score lead were displayed at handicap stone when loading the SGF of the handicap game, but this bug has been fixed in this release.
-
mouse hover to stop flicker
When the analysis is on, the sub-go board changes rapidly and the change charts change, making it difficult to see. It has been modified so that the change diagram is fixed when the mouse pointer is moved over the sub board.
-
mouse wheel to change variation length
By moving the mouse wheel up and down, you can slowly check the change diagram.
-
left/right click to show nth variation
Click the left and right mouse to display the nth change diagram.
-
Addition of "No Refresh Displayed Variation" option
On the main board, if you hover the mouse cursor over the candidate hand with analysis turned on, the various change charts will change rapidly and it will be difficult to see. You can fix the change chart by enabling this option.
The icons on the taskbar are similar to Sabaki's and hard to distinguish, but the new logo looks like lizzie.
This was applied in Lizzie-v0.7.4, but not in Lizzie-improved-v1.3, so I applied it in this release.
These are not functionally explained in particular. If you are interested, please click here
The stone on the sub board has a move number, but there was a bug in Lizzie-v 0.7.4 where this number disappears when you move the mouse cursor to the same position on the main board. This bug has been fixed in this release.
Setting Settings> Engine> Avoid Keep Variations to "0" disables this feature and instead enables the "Undo" feature by right-clicking. (When the engine is Leela Zero)
In panel UI mode, right-clicking anywhere other than the main board did not respond (except for the sub board), but it has been fixed so that the "Undo" effect appears.
Switch to panel UI mode and line up some stones on the board. Next, put back the stones that were lined up. Left-click to place the stone in the same position as it was originally lined up. The stone will not be displayed by itself. Move the mouse cursor to see the stones. It's a very small detail, but it has been fixed so that the stone is displayed the moment you left-click.
Suppose you currently have 10 candidate moves on the main board. By clicking left and right on the sub board, the change diagram from 1 to 10 is displayed. And the number of the change diagram is displayed at the bottom right of the sub board. At this time, there was a bug that the wrong number "11" was displayed. This bug has been fixed in v1.5.
Resolved an issue where existing files were not displayed when saving the file.
Resolves an issue where uppercase .SGF and .GIB files could not be loaded.
As shown in the screenshot below, you can freely edit the pull-down menu display when selecting an engine by adding an arbitrary engine name to the beginning of the engine command.
You can now zoom in / out the winning percentage graph by clicking the center of the mouse.
The settings of various panel displays are stored in lizzie and will be reflected at the next startup.
Solved the problem that the status display at the bottom left was slightly shifted downward when in panel UI mode.
-
Fix forever "Engine is loading..." if pondering is off
Fixed an issue where when lizzie was started, if the analysis was stopped before the analysis was started, the status display at the bottom left would remain "Engine is loading" indefinitely.
-
Fix unshown "Engine is loading..." until mouse move
Solved the problem that "Engine is loading" was not displayed until the mouse was moved when switching the engine.
Solved the problem that the status display at the bottom left was not updated even when switching analysis on / off.
Place some stones on the main board when in panel UI mode. Exclude the next stone and place it in the same place you first placed it. At this time, there was a problem that the change diagram on the upper right was not updated correctly. It has been fixed in v1.6.
In the official release version of Lizzie-v 0.7.4, there is a bug that the analysis result is not displayed even if the sgf file containing the analysis result is loaded, but in the Lizzie-improved series, this bug is not present.
- In Panel UI mode
- The blunder color of the current node is not visible when analysis is turned on. If analysis is turned off, you can see it.
- When a node is moved, the blunder color of the current node is not visible. When analysis is on, it becomes visible by turning analysis off, and when analysis is off, it becomes visible by turning analysis on and off.
- In normal mode
- When a node is moved, the blunder color of the current node is not visible when analysis is off. It is still visible when analysis is turned on and then turned off again, but it disappears again when you move to another node and come back.
- There is no black dot in the "□" of the root node (with no stones in the board).
All of these things have been improved in v1.7.
- If you enter blunder color, lizzie will not remember it unless you click on another cell.
- When I try to delete them all, the last line remains. When I click on another cell, it disappears.
- Threshold values are not reflected in the variation tree unless they are sorted in order of decreasing value, but because the system is not equipped with a sorting function (to sort data according to a certain criterion), it will not work well if the data are entered in pieces.
- Even if you enter a single threshold or blunder color, it will not be reflected until you restart lizzie.
- If the threshold is entered by mistake in full-width characters, the analysis on/off will not work, but users are likely to be confused because there is no function to inform them of the error. The fixed version informs the user that an invalid string has been entered by displaying "-777.0" the next time the user checks.
- You have to restart lizzie to get the new settings for the win rate change nodes.
All of these things have been improved in v1.7.
To make it easier to recognize the function of the win rate change node, the sample data for a one-time function is pre-set.
With the existing lizzie, some parts of it are not displayed correctly in the existing lizzie, so you can move to another tab and come back to it.In v1.7, it is correct from the start.
For example, if a file called "ff.sgf" already exists and you try to save the file by typing "ff", the existing lizzie will be overwritten without a confirmation message, but in v1.7, a confirmation message is shown.
Leela 0.11.0 is now available in lizzie. Download "Leela 0.11.0 engine only" from https://www.sjeng.org/leela.html and place "Leela0110GTP.exe" or "Leela0110GTP_OpenCL.exe" in the lizzie folder. Specify "Leela0110GTP.exe -g" or "Leela0110GTP_OpenCL.exe -g" in the engine command.
When you enter a threshold for a win rate change node, if you enter a string other than an appropriate string, the cell will be surrounded by a red frame and you will not be able to enter blunder color. This allows the user to readily recognize that the wrong string has been entered.
For blunder color, it is now possible to specify the normal movement as well.Until now, the best moves and movements close to them were white and inconspicuous, but with the addition of this function, it is now possible to display good movements in cool colors such as light blue.
On a CPU-only PC, under the conditions of Panel UI + Toolbar + KataGo (OpenCL), the undo speed may be quite slow (about 0.5 seconds per move).This issue has been resolved.
">>" on the lower toolbar is a function to advance 10 moves, but there was a bug that only one move was actually advanced, so I fixed it.
There was a bug that the variation tree protruded to the main board when the winning percentage graph or the sub board was enlarged and displayed when there were many branches in the variation tree. It has been fixed in v1.8.
- Fixed an issue where move numbers were hard to see due to the green winning percentage line.
- By displaying something like "white +0.5" above the bar graph, the current score lead information is easier to see.
- Place some stones on the main board with pondering off. Next, turn on pondering and return the stones one by one. At this time, the stdev and score lead information is hidden. Fixed this issue.
Display the ownership mark with "katago posture" on the toolbar. Then turn off podering and resize the window. Then the ownership mark is not optimized for the window size. Hide this false display. It will be displayed again as soon as you turn on pondering.
Place the stone in the place of the candidate hand displayed on the board. Restoring the stone with the up arrow key or the mouse wheel (up) without moving the mouse pointer. The stone you put on it should disappear, but it doesn't actually disappear. This issue has been fixed in v1.8.
When adding and saving the analysis data to the SGF in which the analysis data by lizzie is recorded, it sometimes took an unusually long time for the numerical values on each candidate to move. In addition, there was a bug that the amount of analysis displayed in the comment column at the bottom right was incorrectly recorded as about 10 times the value on the board. It has been fixed in v1.9.
Previously, when the phase was moved, the display of the total analysis amount on the upper toolbar was the value of the previous phase, but in v1.9 it has been improved to display the total analysis amount stored for each phase. It has been.
When you move the mouse cursor to the engine selection pull-down menu, the engine command string pops up for a few seconds.
If you load an SGF that uses a non-ASCII code (other than half-width alphanumeric characters, Japanese, etc.) as the player name and then save it, there was a bug that the player name at the bottom of the board would be written strangely.In v1.9 this issue is resolved by forcing UTF-8 when saving the SGF.
The Korean notation has been improved to make it easier to use. (I can't explain because I don't understand Korean) See here for more information.
Analysis hung bug when turning on KataGo's estimated area display on a rectangular board.This bug doesn't seem to occur in Lizzie-improved-v1.9, but it seems to occur in the official version of Lizzie-0.7.4.
This issue has not been reproduced and cannot be explained in detail. Since a bug in Ubuntu has been reported, it may be a bug limited to Ubuntu.
- We have also incorporated the new features introduced in KaTrain 1.7 into lizzie. You can specify a rectangular area to limit the analysis within that area.
- Alt+drag to set region of interest.
- Alt+click to reset it.
Leela 0.11.0 and colab-katago were blank in the engine menu, but now they are displayed by entering a nickname.
- In v2.1, all the change diagrams presented were also limited to the specified area, but in v2.2 the entire board is used.
- In v2.1 it was limited to normal mode, but in v2.2 it can also be used in panel UI mode.
- In v2.1, if you release Alt before the mouse button, the area specification will fail, but in v2.2 it will be valid.
- You can now cancel the set analysis area by clicking "Allow" or "Avoid" in the right-click menu. (Only when the engine is Leela Zero and Settings-> Engine-> Avoid Keep Variations is other than 0)
We have revived the score mode, which has been abolished since the score estimation function using zen was applied. Click "Game" on the top toolbar and "Score game" is added at the bottom. In Score mode, by left-clicking on the dead stone, the numerical value of each other's fixed place considering Komi will be displayed in the Agehama display.
"Help" has been added to the far right of the top toolbar. Help → Keyboard controls is a link to a page explaining lizzie shortcut keys.
"Rule" has been added to the "Analysis" menu on the toolbar, and you can now freely choose from 11 types of rules. This feature is only available if the engine is KataGo. In panel UI mode, the selected rule is displayed above the Komi display.
In English mode, there was a typo in the contents of the dialog box displayed by selecting "File"-> "Open from online". Before modification: Please input a available url. After modification: Please input an available url.
If you run the automatic analysis at the end of the game (without the next move), lizzie will be unresponsive. Therefore, "No next move" is displayed in the dialog box.
If you load an SGF that has "BR" or "WR" properties, the rank of each player will be displayed at the bottom of the board.
Since the rule selection function was applied in v2.2, even if the rule is set to "japanese" in the configuration file, it remains "tromp-taylor" in lizzie. You can change it to "japanese" in lizzie, but to avoid confusion, I changed it so that "japanese" is applied by default when lizzie is started. Also, in the list of rule changes, "japanese" is placed at the top.
The move number is displayed in the variation tree.
By pressing the "D" key, you can now switch the display contents of the candidate move. "Normal display"-> "Scorelead + number of searches"-> "Win rate + number of searches"
When the mouse cursor is placed on a candidate move and the R key is pressed, the change diagram is automatically replayed, but until now, even if the analysis was turned off, the analysis was automatically turned on after the automatic replay was finished. This is inconvenient if you want to observe the change chart slowly, so we have changed it so that if you turn off the analysis and perform auto-play, the analysis will remain off even after the auto-play is finished.
You can adjust the opacity of the candidate move with Ctrl + Shift + PageUp / Down, but the amount of change at one time has been slightly increased.
As a function limited to the panel UI mode, there is a function that you can check the change diagram one by one by scrolling the mouse up and down or the arrow keys up and down on the candidate move. In normal mode, you can get the same effect by holding down the Z key and performing the same operation, but in v2.4, it has been improved so that you can operate without the Z key as in the panel UI mode. In addition, there was a small bug regarding this function. There was a bug that did not respond only to the first "↑" or up scroll. It has been fixed in v2.4.
This is a function limited to the panel UI mode, and there is "Add as branch" by right-clicking on the candidate move. By doing this, you can add the change diagram shown by AI as a branch. I think it's a very convenient function because you can record the reference map shown by AI with one touch without manually arranging the stones one by one. Previously it was a function limited to the panel UI mode, but in v2.4 this function can also be used in the normal mode. There was also a small bug with this feature. There was a bug that the color of the added branch stones would be reversed black and white when using this function when there were no stones on the board yet. It has been fixed in v2.4.
When you place the mouse cursor on the candidate hand and hold down the "Z" key and scroll the mouse up or down or check the change diagram with the up and down keys of the cursor, the stone has not been displayed on the board until now. It was a specification to arrange the stones, but in v2.4 it is a specification to arrange the stones with the start number displayed in advance.
In the input of leelazero and sai engine commands, I think that one normal space is inserted after "-w" or "--weights". If the number of spaces is 0 or 2 or more, the engine will start but the engine menu field will be blank. Previously this was the specification, but in v2.4 it has been changed so that even if the number of spaces is 0 or 2 or more, it works as if it had one space.
Only in v2.2 and v2.3, there was a problem that suddenly warped to the past node when arranging stones in panel UI mode. It seems to be a bug related to the function that limits the analysis area, but it has been fixed in v2.4.
There was a bug that "1" was not displayed on the first stone when placing a stone on an empty board. This bug was not in the official version of lizzie-v0.7.4, but only in the improved version of lizzie. It has been fixed in v2.4.
Suppose you have created a variation tree like the one on the left. The figure on the right is two steps from the figure on the left, but it looks like the branches are separated. To eliminate this unnaturalness, we added a line at the top. Also, if the start number is right next to the node, it often overlaps with the line, so I fine-tuned it to the lower right of the node.
"(; (; B [aa] (; W [da]) (; W [ea] (; B [fa]) (; B [ga]) (; B [ha]) (; B [ia]) (; B [ja]) (; B [ka]) (; B [la]) (; B [ma]) (; B [na]) (; B [oa]) (; B [pa]) ( ; B [qa]) (; B [ra]) (; B [sa]))) (; B [ab]; W [bb])) " Please save this data in SGF format and load it into lizzie-improved-v2.3. Then hit A-18 with the first move. A-18 is a movement included in the variation tree, but the movement of A-18 is not actually reflected in the variation tree. The figure on the left is v2.3 and the figure on the right is v2.4 (improved).
