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

Some engines won't show arrows #236

Open
haochiwocao opened this issue Jan 27, 2022 · 2 comments
Open

Some engines won't show arrows #236

haochiwocao opened this issue Jan 27, 2022 · 2 comments
Labels
bug Something isn't working

Comments

@haochiwocao
Copy link

For example this one http://rebel13.nl/windows/rebel-14.html but actually a lot of them. Some engines (like this one http://www.pkoziol.cal24.pl/rodent/rodent.htm) will show arrows ONLY of it is set to use 1 thread and not less than 2 MultiPV

@haochiwocao haochiwocao changed the title Some engines just won't show arrows Some engines won't show arrows Jan 27, 2022
@QueensGambit QueensGambit added the bug Something isn't working label Feb 3, 2022
@QueensGambit
Copy link
Collaborator

Thank you for the bug report. 👍

@ksthicke
Copy link
Contributor

I tried Rodent to investigate what is going on. (The download links for Rebel weren't working.) Some things I learned:

  1. There is indeed an issue when MultiPV is set equal to 1. The issue is that the engine outputs only pv, instead of multipv, but Liground is only looking for multipv. This should be a straightforward fix that I plan to do. I ran into this same issue with Leela Chess Zero, so I was planning to fix this anyways.
  2. When the number of threads is greater than 1, the engine does not always output more than one line, even when MultiPV is set to a number greater than 1. (Liground still plots the arrow for the one line that gets output.) Therefore, this is not a bug with Liground; this is an issue with the engine.
  3. Rodent also has an option to use book moves. When this is enabled, the engine does not do any sort of analysis during the first few moves; it just looks at an opening book and outputs the move it wants to play. Since there is no analysis being done by the engine, there is not really anything for Liground to show with arrows. If you disable the "UseBook" option in the engine settings, then the arrows work just fine (modulo the points above).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants