Repository navigation
Refine good capture ordering by victim value - #18
Draft
KnightStackSys wants to merge 1 commit into
Draft
KnightStackSys wants to merge 1 commit into
KnightStackSys wants to merge 1 commit into
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Stacks on top of
move-ordering-see-splitas a focused incremental move-ordering experiment.Change
SEE >= 0capture bucketpieceValue(victim) * 32)Position::capturedSquareRationale
The first SEE split appears to be testing well. This follow-up tries to improve ordering within the already-good captures by preferring more valuable victims when SEE scores are otherwise close, without changing the broader move-stage ordering.
Scope
move-ordering-see-split, notmainsrc/search.cppchangesFor clean testing, compare this branch directly against
move-ordering-see-split.