Skip to content

About Multiple Engine Support & Heights Switching #356

@zsalch

Description

@zsalch

Hi

I am looking forward to supporting more engines in the next release of the lizzie, such as AQ, Phoenix, Elf, etc. I am prefer to AQ because it uses Japanese rules, and most of AI only support Chinese rules. AQ can make up for this deficiency.

But I also know that supporting a new engine requires more work, so I temporarily made a simple solution that allows Lizzie to switch between multiple weights, which also helps me see the analysis status between different weights.

Because I have not do full tests, so only submitting the changes in my branch. Those who are interested can refer to them(https://github.com/zsalch/lizzie/tree/next_dev).

Change logs:

  1. In the config.txt file, add a configuration (engine-command-list) to add a new command lines:

    "engine-command": "./leelaz --gtp --lagbuffer 0 --weights %network-file --threads 2",
    "engine-command-list": [
      "./leelaz --gtp --lagbuffer 0 --weights leelaz_172_b1c --threads 2",
      "./leelaz --gtp --lagbuffer 0 --weights human_best --threads 2",
      "./leelaz --gtp --lagbuffer 0 --weights elf_1_62b --threads 2",
      "./leelaz --gtp --lagbuffer 0 --weights leelaz_157_d35 --threads 2"
    ],

  1. Use the shortcut key Ctrl+number to switch the weight and display the weight name in the left down:
        Ctrl+0: Default switch to "engine-command"
        Ctrl+(1-9): Switch to "engine-command-list"

  2. If the current node is in Branch, it also supports keeping the current node when switching weights.

The effect is as following:

elf 2 d13:
image
leela zero 172 b1c:
image

Pre-release files:
https://github.com/zsalch/lizzie/releases/tag/v0.5%2B

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions