-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Penalty for a quiet ttMove that fails low
Also the penalty/bonus function is misleading, we should simply change it to stat_bonus(depth) for bonus and -stat_bonus(depth+ ONE_PLY) for extra penalty. STC: LLR: 2.96 (-2.94,2.94) [0.00,5.00] Total: 11656 W: 2183 L: 2008 D: 7465 LTC: LLR: 2.95 (-2.94,2.94) [0.00,5.00] Total: 11152 W: 1531 L: 1377 D: 8244 Bench: 6101931
- Loading branch information
1 parent
471f7a1
commit 5254a60
Showing
1 changed file
with
26 additions
and
13 deletions.
There are no files selected for viewing
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
5254a60
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi Marco Costalba!
I have some questions to ask:
struct StateInfo {
// Copied when making a move
Key pawnKey;
Key materialKey;
Value nonPawnMaterial[COLOR_NB];
int castlingRights;
int rule50;
int pliesFromNull;
Score psq;
Square epSquare;
// Not copied when making a move (will be recomputed anyhow)
Key key;
Bitboard checkersBB;
Bitboard blockersForKing[COLOR_NB];
Bitboard pinnersForKing[COLOR_NB];
// Not copied when making a null move (will be recomputed anyhow)
Piece capturedPiece;
StateInfo* previous;
Bitboard checkSquares[PIECE_TYPE_NB];
};
this gain 1% faster
if (pt == KING)
b &= ~StepAttacksBB[KING][pos.square(~us)];
not:
if (pt == KING)
b &= ~PseudoAttacks[QUEEN][pos.square(~us)];
Please fix it.
5254a60
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@VoyagerOne @mcostalba Could you guys please confirm if this committed patch is exactly equivalent to @VoyagerOne's original "update search" patch? Thank you.