You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was running BayesOpt with ASHA, MSR, FIFO and Hyperband for a project and the tuning jobs would all stop around the 10th-11th training jobs. I tried to verify my code by running the BayesOpt example from the RayTune site. The example tuning job from the RayTune site also terminates at trial 11 even though we expect it to run for 1000 trials. I was able to reproduce this with Ray 1.13.0 and Ray 2.0.0 I also tried the latest bayesian optimization library from #336 and v1.2.0.
The text was updated successfully, but these errors were encountered:
ladyluk
added
bug
Something that is supposed to be working; but isn't
triage
Needs triage (eg: priority, bug/not-bug, and owning component)
labels
Aug 23, 2022
TLDR: set random_search_steps to something higher, or consider using a harder problem.
BayesOpt internally fits a gaussian process in order to generate new trial configurations. Your search space is very small, so it converges pretty fast to an optimal result (height = -100 and width = 20). After that, it just samples the same (optimal) configuration again and again - and those duplicates are skipped, because it doesn't make sense to train a model with the same parameters twice.
If you increase random_search_steps it will sample more truly random configurations before using the GP to sample the configurations. This will increase the number of trials you see.
Please note that this doesn't really make sense with your example as you find the optimal solution in < 10 samples, so it is actually a very efficient way. So instead you should probably just run this on a more complicated problem where the GP does not converge in 2-3 iterations.
krfricke
added
question
Just a question :)
tune
Tune-related issues
and removed
bug
Something that is supposed to be working; but isn't
triage
Needs triage (eg: priority, bug/not-bug, and owning component)
labels
Aug 23, 2022
What happened + What you expected to happen
I was running BayesOpt with ASHA, MSR, FIFO and Hyperband for a project and the tuning jobs would all stop around the 10th-11th training jobs. I tried to verify my code by running the BayesOpt example from the RayTune site. The example tuning job from the RayTune site also terminates at trial 11 even though we expect it to run for 1000 trials. I was able to reproduce this with Ray 1.13.0 and Ray 2.0.0 I also tried the latest bayesian optimization library from #336 and v1.2.0.
Versions / Dependencies
Ray 1.13.0 and 2.0.0
Bayesian-Optimization 1.2.0 and latest install from github #336
Amazon Linux 2
python 3.7.10
Ray 2.0.0
Bayesian-Optimization 1.2.0 and latest install from github #336
macOS Monterey 12.5
python 3.10.4
Ray 1.12.1 and 1.13.0
Bayesian-Optimization 1.2.0 and latest install from github #336
centos stream
python 3.9.13
Reproduction script
Issue Severity
High: It blocks me from completing my task.
The text was updated successfully, but these errors were encountered: