Allow catch kwargs passthrough for optuna's study.optimize() #1
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
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.
Allow catch kwarg passthrough in Trainer.hyperparameter_search(backend="optuna") in order to expose Optuna’s Study.optimize(..., catch=...) argument by popping out catch kwargs before calling Optuna's study.optimize().
Motivation
The current Hugging Face Transformers integration with Optuna does not expose Optuna’s Study.optimize(..., catch=...) argument.
As a result, when a trial raises an exception (e.g., CUDA OOM, data mismatch, tokenizer failure, nan/inf loss), the entire hyperparameter search stops prematurely instead of marking the trial as failed or pruned.
Adding support for a catch parameter—forwarded to Optuna’s backend—would allow users to continue tuning even when individual trials encounter errors.