⌛ Make soft and hard bounds explicit, simplifying the existing logic #664
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.
Reimplementation of #447.
This is an attempt to standarize time management using the hard/soft bound technique, where different values are used to stop the search after each IDDFS iteration (soft bound) and to stop the search at any moment (hard bound).
We were already using this technique via applying
DecisionTimePercentageToStopSearching
coefficient to the hard bound to get the soft one.Last tm revision was done in #288
I run this non-ref tests, but I'm trully merging this together with #665, I just want to make clear the separation between the implementation and the value tweaking (fixing even, lol)