Repository navigation
Tune Null Move Pruning for 4PC - #3
Draft
KnightStackSys wants to merge 6 commits into
Draft
KnightStackSys wants to merge 6 commits into
KnightStackSys wants to merge 6 commits 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.
NMP v1 was trending about -18 Elo after ~200 STC games, so this branch keeps the same reversible null-move infrastructure but makes the pruning policy materially more conservative for four-player Teams chess.
NMP v2 tuning
R = 2 + depth / 4toR = 2 + depth / 6beta) instead of the synthetic null score, preventing optimistic null scores from inflating parent/aspiration valuesUnchanged safety guards
This is intentionally a separate v2 branch so the running v1 STC result stays reproducible. Please SPRT this branch against
mainwith HCE only before merge.