Time handling improvements #8
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
* Use more time at the 'beginning' of the games, where it takes more time to reach the same depth, when no 'moves-to-go' are provided (FirstTimeLimitWhenNoMovesToGoProvided , SecondTimeLimitWhenNoMovesToGoProvided added). We already do something similar with KeyMovesBeforeMovesToGo, CoefficientBeforeKeyMovesBeforeMovesToGo and CoefficientAfterKeyMovesBeforeMovesToGo when 'moves-to-go' are provided. * Add a minimum MinDepth used in each of the moves, avoiding the situation of making moves with depth 3 in the middle of the game. 5 seems the highest value we can go for right now.
…ely, even if MinDepth hasn't been reached. Remove debug logs from console. Add badgest to readme.
…to think < 1s. Also remove clamping
eduherminio
force-pushed
the
time-handling-improvements
branch
from
cace9ed
to
5aec39a
Compare
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.
We already do something similar with KeyMovesBeforeMovesToGo, CoefficientBeforeKeyMovesBeforeMovesToGo and CoefficientAfterKeyMovesBeforeMovesToGo when 'moves-to-go' are provided.
CancellationTokenso that 'stop' commands act immediately, even if MinDepth hasn't been reached.