Hyperparameter tuning, standardization & extended searchspace construction #278
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
…rkhoven/kernel_tuner into searchspace_experiments
…Kernel Tuner for hyperparameter tuning
…yperparamtuner tuning returning more results than the searchspace size
|
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 pull request adds globalized hyperparameter tuning via the autotuning methodology package. This allows for hyperparameter tuning to be conducted over a benchmark set of searchspaces using the methodology quantification. To achieve this, it also adds standardization by implementing the 'T1' standardized input format for Kernel Tuner. In addition, it adds support for pyATF as a searchspace constructor.