Add a UCI implementation #409
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
b4ux1t3
force-pushed
the
uci-implementation
branch
from
ca77e93 to
ccdcad8
Compare
ryanheath
reviewed
Jul 31, 2023
b4ux1t3
force-pushed
the
uci-implementation
branch
from
7fc112b to
e3f11fd
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I started drawing up a UCI implementation that wraps the API.
Currently, it supports most commands, ignoring
quitcommands and just responding that it's ready toisreadycommands.I vetted the functionality by running my bot as a UCI engine with lichess-bot. I appear to have covered all of my bases, though I do not correctly handle the different kinds of go commands at the moment.
I ran into a few problems when working with the engine, and have hacked around them as best I can.
Any help from the maintainer in addressing some of the issues (through application of actual understanding of the library, as opposed to blindly bashing things together until they work) would be greatly appreciated.
I believe this satisfies #145, as well as any other open issues about a UCI implementation.