-
Notifications
You must be signed in to change notification settings - Fork 217
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
SMAC stops before n_trials #1088
Comments
@mfeurer Great, thanks for the clarification! Do you know if this can be disabled? I'm perfectly happy hacking around in the source code if needed. |
No, sorry, I don't know if this can be disabled or where the number of retries can be increased. |
Okay, thanks! I'll look at it on my end and let you know if I find a simple way around it. |
Hi @hvarfner, sorry for the late reply, but we had some people being absent during December and there was the Christmas break. However, if you have not found a solution, you could try to increase the number of retries or fiddle manually with the code in the config_selector.py (iteration function) to avoid this behavior. However, I believe that this is rather a bug then a configuration problem as you have set the iteration limit already to 500 in the intensifier, but this is apparently not propagated to the config_selector. This is something we should be looking into, thanks for posting. |
A rather basic question, possibly related to previous issue by mfeurer regarding
n_retries
:Using the following setup (and latest pip version, 2.0.2):
for a fully categorical, slightly constrained (one forbidden-clause which excludes ~20% of the search space of 300k configurations), SMAC stops after 64 iterations with the following message:
Why is this, and can it be disabled so that the run can finish? I tried to examine the
Intensifier
but was unable to find the solution myself.Any help would be much appreciated!
Best,
Carl
The text was updated successfully, but these errors were encountered: