-
Notifications
You must be signed in to change notification settings - Fork 228
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
About Multiple Engine Support & Heights Switching #356
Comments
Wow~ this is great~~~ |
I saw that there're more configs in the config file. |
I haven't run this to try it out yet, but in principle it seems amazing. Quick question - are all of the engines in the command list being run in the background at once, or does it shut off the previous engine and spin up the new one only when it's activated with the Ctrl+# shortcut? If so, does that mean you have to wait for weights to be loaded every time? Or are you doing something clever with suspending the process in the background? (In which case VRAM might still be an issue on some cards, right?) |
@apetresc |
@wonsiks |
@zsalch I tried "Multiple Engine" and it worked on my PC (win10/i7-8700k/1080ti), |
@zsalch |
... and the latest version (Windows) supporting dynamic komi is available at https://github.com/alreadydone/lz/releases/tag/komi%2Bv0.42 or you can compile it from https://github.com/alreadydone/lz/tree/komi+next |
@atoutw For the display of the comment, please open the display variation graph, as long as there is a C tag in sgf, it can be displayed. This change has been submitted pull request, has not yet been agreed, please temporarily use my attachment. |
@alreadydone |
@zsalch Thanks for teaching the way to display of the comment, but how could I be able to change the words' size of the comment? |
@atoutw |
@zsalch There are some bugs(I think) I found in pre-release. Please check them.
|
@atoutw About 1&2, would you like to upload the sgf file? and provide more detailed explanation? |
@zsalch I will try to provide explanation more easily... About 4, There is still some little problem about comment as below. May I write another suggestions of the next version here? |
I suggest showing weight file name on the window title bar instead of bottom left side of the screen. |
@wonsiks |
@atoutw About 4, I will add a little padding. About other suggestions, I recommend creating a new issue, so that more person will see it and it may be resolved faster. |
@zsalch step 1. Input the game's moves and variations in MultiGo, and save it by MultiGo. step 2. Open it by Lizzie v0.5+ and show the first variation, then save it by Lizzie v0.5+. I will stop here because there is a seriouser problem I just found and I will post them in next comment. |
@zsalch ・step 1. Input the game's moves and variations in Lizzie v0.5+.
・step 2. Copy (step 1) and paste it in another Lizzie v0.5+.
It is strange that the two go board is not the same. ps. I used this night's update of Lizzie v0.5+. |
@atoutw |
@atoutw |
@zsalch |
@zsalch |
@zsalch
See some suggestions about using it under 6.5 komi (as well as other instructions) in leela-zero/leela-zero#1772 (also see leela-zero/leela-zero#1599 for discussions).
You may compile the latest komi+next branch. Issue alreadydone/lz#57 may need merging latest gcp/next to be solved. |
@alreadydone |
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:
"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"
],
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"
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](https://user-images.githubusercontent.com/42595514/44957152-37280d80-af01-11e8-9fe7-704f776d77f4.png)
![image](https://user-images.githubusercontent.com/42595514/44957360-0c8b8400-af04-11e8-8304-1fca055c98af.png)
leela zero 172 b1c:
Pre-release files:
https://github.com/zsalch/lizzie/releases/tag/v0.5%2B
The text was updated successfully, but these errors were encountered: