Skip to content
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 the display method when switching engines #785

Closed
hope366 opened this issue Oct 15, 2020 · 3 comments
Closed

About the display method when switching engines #785

hope366 opened this issue Oct 15, 2020 · 3 comments

Comments

@hope366
Copy link

hope366 commented Oct 15, 2020

You can see the name of the weight file in the pull-down menu on the top menu to switch engines.
When the same weight file "KataGo40b" is used with different engines, KataGo-v1.6.1-OpenCL and KataGo-v1.6.1-CUDA, the pull-down menu shows exactly the same name, "KataGo40b", which is very difficult to distinguish. It is.
It's possible to have two files that are identical and have different filenames, like "KataGo40b-1.6.1-OpenCL" and "KataGo40b-1.6.1-CUDA", but that's a bit tricky.
It would be useful if you decide on an arbitrary nickname that is easy to understand and the nickname appears in the pull-down menu.
Sabaki uses this technique, and I find it useful.

@hope366 hope366 changed the title Display when switching engines About the display method when switching engines Oct 15, 2020
@NTUST-MITLAB
Copy link

Without a rework and adding additional fields for aliases to different engine settings (it would involve saving alias, manu item layout arrangement, even submenus), the easiest way to tell the difference as a temporary fix is to change the public void updateEngineMenu(List<Leelaz> engineList) in Menu.java to show the full engine commands. Instead of appending engineDt.currentWeight() to each item, appending engineDt.engineCommand()

@hope366
Copy link
Author

hope366 commented Oct 17, 2020

Thank you for showing me how to make useful changes.

無題
I think it's a great idea in the sense that it's possible to completely distinguish between the different engines.
On the other hand, the display content may be long and somewhat difficult to read visually.
It's also a shame that you can't add your own favorite information such as "analysisWideRootNoise = 0.0" or "rules = japanese".

@hope366
Copy link
Author

hope366 commented Oct 18, 2020

Thank you for your prompt response as usual.
無題

kaorahi pushed a commit to kaorahi/lizzie that referenced this issue Oct 24, 2020
commit 8bf2209
Author: Hiraoka <[email protected]>
Date:   Mon Oct 19 21:32:00 2020 +0900

    fixup

commit 33cb711
Author: Hiraoka <[email protected]>
Date:   Sun Oct 18 00:05:28 2020 +0900

    fixup

commit bf96dcc
Author: Hiraoka <[email protected]>
Date:   Sat Oct 17 23:55:27 2020 +0900

    Quick hack to support featurecat#785 (<nickname> before the engine command)
@hope366 hope366 closed this as completed Nov 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants