Add possibility to suggest bounds of a float hyperparameter #242
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.
Thanks to the new attributes (and corresponding
suggest_with_optuna()
arguments)suggest_low
andsuggest_high
, we enforce the possibility of suggesting lower or upper bound.Indeed, by default, optuna will suggest inside the range (low, high) but never reach exactly a bound (except if a step was provided).
To achieve this, a derived categorical hyperparameter is suggested under the hood to decide whether suggesting the lower bound, upper bound, or a float in between. The "generated" hyperparameter will be named as the original hyperparameter, suffixed with ".suggest_bound" and will take as values