[Optuna Sweeper Plugin]: Add user attributes to Optuna trial #2718
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
facebook-github-bot
added
the
CLA Signed
domvwt
changed the title
|
@domvwt could you please give some motivation for this PR? What use case does this enable? What is the change in API that is exposed to users? |
|
Hi @Jasha10, the motivation here is to allow users to define User Attributes on Optuna trials. There is currently no way to do this but the capability has been requested in issue #2293. I want to be able to log additional performance metrics for trained models and other metadata for audit purposes, such as the dataset used and library versions. |
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.
Motivation
Add capability to log additional attributes against Optuna trial runs.
Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
This is a draft PR, tests are not yet implemented (if applicable).
Related Issues and PRs
Issue: #2293
TODO