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 want to make use of priors in my SMAC runs, but whenever I add a parameter with a prior to my configspace, it results in half of my trials getting an infinite cost value since they don't finish running.
Hi Diederick,
I am now trying to investigate this issue
First and as a side note: to use Priors properly, you need to use the PriorAcquisitionFunction as given in the example. Your provided code block does not do that, the quoted example does.
PriorAcquisitionFunction(
acquisition_function=HyperparameterOptimizationFacade.get_acquisition_function(scenario),
decay_beta=scenario.n_trials/10, # Proven solid value
)
Secondly, I agree that this is a confusing issue. I think this is likely connected to DASK because my execution of your code also ends in a DASK error. How critical is it for you to use multiple workers? We are not sure whether there is a simple fix for this issue.
Description
I want to make use of priors in my SMAC runs, but whenever I add a parameter with a prior to my configspace, it results in half of my trials getting an infinite cost value since they don't finish running.
Steps/Code to Reproduce
I took the configspace example from https://automl.github.io/ConfigSpace/latest/guide/#5th-example-placing-priors-on-the-hyperparameters, added a fake evaluation function with a simple HPOInterface:
The same occurs when using the example from https://automl.github.io/SMAC3/main/examples/1_basics/6_priors.html and adding n_workers=2 to the scenario (and replacing the evaluation function with a random number to save time testing).
Snippet from a runhistory file to illustrate:
Expected Results
A normal SMAC run
Actual Results
A run in which half of the configurations don't finish running / time out (even though there is no evaluation function which takes time).
Versions
Tested on Python 3.10 and 3.11.2, with smac==2.3.0 and configspace==1.2.1
The text was updated successfully, but these errors were encountered: