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

Documentation #12

Open
geoff-m opened this issue Apr 6, 2024 · 3 comments
Open

Documentation #12

geoff-m opened this issue Apr 6, 2024 · 3 comments

Comments

@geoff-m
Copy link

geoff-m commented Apr 6, 2024

The readme says

For each move available at the current position, print the move and the number of nodes at the given depth which are an ancestor of that move, separated by whitespace.

Does "the current position" mean the same thing as what you call "the base position" earlier in this section? If not, what does "the current position" mean?

Also, you meant descendant instead of ancestor, right?

@agausmann
Copy link
Owner

Starting at the "base" position (i.e. $fen, set by the fen command), your engine should apply the moves provided in the $moves list (modified by the move/unmove/moves command) to get to the "current" position, from which it executes the perft.

Yes, that should be "descendant", thanks.

@geoff-m
Copy link
Author

geoff-m commented Apr 6, 2024

Oh, now I understand. I was thinking the optional move list represented moves that should each be played in the given position (effectively selecting multiple branches starting at the root), not a sequence of moves to be played one after the other (effectively selecting a single deep branch).

@agausmann
Copy link
Owner

Would you mind taking a look at #14 ? I've tried to reword those docs to hopefully make it more clear in general.

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