bsamseth / Goldfish

86%

master: 92%

LAST BUILD ON BRANCH v1.8.2

branch: v1.8.2

CHANGE BRANCH

x

Reset

• v1.8.2
• TTable
• action-build
• aspiration-window
• benchmarking
• castling
• code-style-fixes
• delta-pruning
• evaluation
• futility-pruning
• killer-move
• lichess-bot
• master
• move-ordering
• movegen
• nega-scout
• null-move-pruning
• pawn-evaluation
• piece-square-tables
• pointer-removal
• pv-search
• redesign
• refactor
• refactor-code-base
• search-refactor
• syzygy-tb
• uci
• uci-options
• unittest
• v0.1
• v1.0
• v1.1
• v1.11.0
• v1.11.1
• v1.11.2
• v1.12.0
• v1.13.0
• v1.2
• v1.3
• v1.4
• v1.5
• v1.5.1
• v1.6.0
• v1.7.0
• v1.7.1
• v1.8.1
• v1.9.0

Build # 262

Build Type

push

travis-ci

Committed by bsamseth

Commit Message

Bugfix: Don't save quiescent results in ttable (#25)

I had originally thought that storing quiescent results with a depth of
zero would be safe (motivated by imporved benchmark scores (not noticing
the changes in evaluations...)). Turns out, this is not the case.

This is stated among other places in "Replacement Schemes for
Transposition Tables", D.M. Breuker, J.W.H.M. Uiterwijk and H.J. van den
Herik.

Removing the ttable saves in quiescent search resolves the issues
motioned in #25.

Fixes #25.

Run Details

942 of 1095 relevant lines covered (86.03%)

9807312.18 hits per line