Skip to content

Conversation

@FauziAkram
Copy link
Contributor

@FauziAkram FauziAkram commented May 4, 2017

Replacing the old Protector table with a simple linear formula which takes into account a different slope for each different piece type.

The idea of this simplification of Protector is originated by Alain (Rocky)

STC: LLR: 2.95 (-2.94,2.94) [-3.00,1.00]
Total: 70382 W: 12859 L: 12823 D: 44700

LTC: LLR: 2.95 (-2.94,2.94) [-3.00,1.00]
Total: 61554 W: 8098 L: 8031 D: 45425

Bench:6231822

@MichaelB7
Copy link
Contributor

I like the changes in evaluate.c, by why change types.h at the same time? Is it not best to change the those values through a tuning run?

@FauziAkram
Copy link
Contributor Author

Hi Michael,
this new implementation of King Protector uses a factor which keeps on decreasing the value of a piece based on the distance of each piece, so its obvious that we need to compensate a little the base value of the pieces in order to not decrease too much their values, so if you look at the tune, you will see a value called ProtectorDelta , that is exactly the exact value that we need to change from the base value of the piece to compensate for such a change.

@zamar zamar closed this in 6b4959e May 8, 2017
MichaelB7 pushed a commit to MichaelB7/Stockfish that referenced this pull request Apr 23, 2020
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

Successfully merging this pull request may close these issues.

2 participants