Virtual_Visit, Virtual_Mix, Virtual_Offset#205
Merged
QueensGambit merged 34 commits intomasterfrom Aug 8, 2023
Merged
Conversation
also only increase virtualLoss Counter by 1
+ use also virtual-visit of 1 + don't use additional vector operation
get_transposition_q_value()
Rename VIRTUAL_LOSS into VIRTUAL_WEIGHT Replace virtualVisitIncrement by virtualMixThreshold
Switch between VIRTUAL_OFFSET and VIRTUAL_VISIT when using VIRTUAL_MIX
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.
This PR adds Virtual_Visit, Virtual_Mix and Virtual_Offset as additional Virtual_Styles compared to Virtual_Loss.
The new default is Virtual_Mix which switches from Virtual_Visit to Virtual_Loss when a number of Virtual_Mix_Threshold (default: 1000) has been reached.
Using Virtual_Visit for low number of moves leads to a significant Elo advantage (101.1 +/- 19.4) in low time-control / low number of nodes.
There has been a problem connected to USE960. That's why it has been disabled for now.
Also an initialization problem in
first_and_second_max()has been fixed.