-
-
Notifications
You must be signed in to change notification settings - Fork 227
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
Alternative termination features other than max iteration? #877
Comments
That would be indeed beneficial. I will integrate this feature in our upcoming Version 2.0.
Does this work for you? |
I just implemented it: |
I'll also add that you can pass custom callbacks to SMAC with You can use this test as a reference, I also implemented a really dumb version early stopping you can use if you need, with an example in this PR in auto-sklearn but you would have to wrap it in |
From @renesass in the other issue, you can use what I suggested for now but this will change significantly in the next release by the looks of things.
|
|
The documentation still has to be updated drastically. But you could use following examples already: https://github.com/automl/SMAC3/blob/development-2.0/examples/mlp_multi_fidelity.py or also the other examples but you have to set deterministic in the scenario to false (a bug i just discovered...).
|
Are there other features that we can use to terminate the optimization other than setting max iteration number (set by 'runcount-limit' in Scenario)?
For example, termination when the difference between expected (estimate) and given value of the function is less than some threshold for some number of iterations.
The text was updated successfully, but these errors were encountered: