add default optimization direction for 'fitness' and 'cost' #323
Conversation
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
As we extend to more optimization objectives and explore constrained optimization it happens more often that we have a user-defined metric that defines the optimization objective. This pull makes it easy to specify the optimization direction, without the need to explicitly specify the direction using the ``objective_higher_is_better=`` option of ``tune_kernel()``. Now, if your objective is named ``"fitness"`` Kernel Tuner assumes maximization and for objectives named ``"cost"`` or ``"loss"`` minimization is assumed.
|
stijnh
approved these changes
Jul 16, 2025
|
Looks good to me! |
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.
As we extend to more optimization objectives and explore constrained optimization it happens more often that we have a user-defined metric that defines the optimization objective. This pull makes it easy to specify the optimization direction, without the need to explicitly specify the direction using the
objective_higher_is_better=option oftune_kernel(). Now, if your objective is named"fitness"Kernel Tuner assumes maximization and for objectives named"cost"or"loss"minimization is assumed.