Repository navigation
feat(eval): tunable 4PC Teams rook evaluation - #56
Open
KnightStackSys wants to merge 2 commits into
Open
KnightStackSys wants to merge 2 commits into
KnightStackSys wants to merge 2 commits into
Conversation
This branch has not been deployed
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.
Summary
Adds a dedicated
rook_eval.cppmodule and 11 UCI-tunable rook feature weights, wired into the existing hand-crafted evaluation with the established Red+Yellow vs Blue+Green score convention.Features
EvalRookPawnlessBonusper rook as the original 32 4PC pawns disappear.New UCI spin options (0–100)
All options accept
setoption name ... value ..., appear inuciandtuneparams, and reset throughResetTuning. Values are starting hypotheses, not empirically tuned.Verification
ironphoenix_rook_featuresto CTest, covering tuning limits/reset/options, file and phase conditions, rotated opponent home lines, both passed-pawn categories, sliding blockers, castle-right-dependent king blockage, queen-file pressure despite screens, teammate rook connections, and side-to-move team sign.Testing recommended before merge
Run CMake/CTest in CI, then A/B STC and LTC matches (single feature weights toggled to zero and combined feature set). Profile NPS in tactical/open and closed positions. Do not treat these initial constants as proven Elo gains.