-
Notifications
You must be signed in to change notification settings - Fork 7.1k
[tune] Add Initial Parameter Suggestion for HyperOpt #3944
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[tune] Add Initial Parameter Suggestion for HyperOpt #3944
Conversation
|
Test PASSed. |
|
Can you amend the Right now, I did a quick test of this and I got an error: Code I ran: Is there something I did wrong? |
|
Test PASSed. |
|
Ah almost certainly a bug on my end, I only tested it with non-choice params. Let me investigate and I'll fix it up and provide the example you suggest |
…cumentation for HyperOpt to fix a mistake and reflect a fix for using choice parameters
|
@richardliaw The issue was that generate_trials_to_evaluate wants the index of the choice rather than the choice value itself. I considered trying to keep the same interface and to work it out for the user but it'd be a bit messy, so just opted for explaining this in the example / documentation as it's not that complex (and will also be more of a 'drop in' for users of hyperopt who want to run their code on Tune). I've fixed up the example and it runs fine for me now. Let me know your thoughts and if you've any further changes. |
|
Test PASSed. |
Co-Authored-By: markgoodhead <[email protected]>
|
Test FAILed. |
|
jenkins retest this please |
|
^ is that how you're meant to kick off new tests if the previous ones failed due to unrelated flakiness? |
|
Test PASSed. |
richardliaw
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yep - looks good, thanks a bunch for this contribution!
Similar to the recent change to HyperOpt (##3944) this implements both: 1. The ability to pass in initial parameter suggestion(s) to be run through Tune first, before using the Optimiser's suggestions. This is for when you already know good parameters and want the Optimiser to be aware of these when it makes future parameter suggestions. 2. The same as 1. but if you already know the reward value for those parameters you can pass these in as well to avoid having to re-run the experiments. In the future it would be nice for Tune to potentially support this functionality directly by loading previously run Tune experiments and initialising the Optimiser with these (kind of like a top level checkpointing functionality) but this feature allows users to do this manually for now.
What do these changes do?
Allows users of the HyperOptSearch suggestion algorithm to specify initial experiment values to run (typically already known good baseline parameters within the domain specified)
Related issue number
Discussed in the ray dev forums