Adjust mobility values #7
Merged
Conversation
This file contains 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
…ce in the 1k+ test fens
eduherminio
force-pushed
the
adjust-mobility-values
branch
from
14de51e to
c44ce0f
Compare
eduherminio
added a commit
to lynx-chess/Lynx
that referenced
this pull request
May 31, 2024
Move mobilty common value/offset back to piece values, being able to better understand real mobility values and avoiding having weird piece values. This is, at the end of the day, very similar to what is done with PSQTs. The main difference is that there I take the average of the table, and here I take the first non-zero value as offset. Negative values at the beginning of bishop mobility array never get hit. That means that they're not excluded from the tuning, but they're never hit during it (for now) Comes after some hard work in lynx-chess/texel-tuner#7
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.
Move mobilty common value/offset back to piece values, being able to better understand real mobility values and avoiding having weird piece values.
This is, at the end of the day, very similar to what is done with PSQTs. The main difference is that there I take the average of the table, and here I take the first non-zero value as offset.
Negative values at the beginning of bishop mobility array never get hit. That means that they're not excluded from the tuning, but they're never hit during it (for now)
lynx-chess/Lynx#788