-
Notifications
You must be signed in to change notification settings - Fork 1.3k
[Question] Modify Stopping Criterion to Accuracy #1624
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
Comments
Hi @DarkEol, The The @aron-barm Might have more to say on this |
@eddiebergman thank you for the response! I see that |
SMAC (from which Please not that this is still version tldr; If you used accuracy as the optimization metric, (The This means |
Uh oh!
There was an error while loading. Please reload this page.
Hi,
I have seen that stopping criterion can be changed to number of evaluations using smac_scenario_args 'runcount_limit' param (451) or limited by cost value using callback function (Early stopping and Callbacks).
But is there a way to set accuracy as a stopping criterion? So that after some level of accuracy was reached stop the search. I see that there is "termination_cost_threshold" parameter in SMAC, can I use it from Auto-Sklearn? Or maybe there is another way to to set accuracy as stopping criterion?
The text was updated successfully, but these errors were encountered: