Open dhristozov opened 1 month ago
@dhristozov Hi, thank you for identifying this issue! Could you try the updated code (main branch) again and let us know if it works now?
@xuyuting , thanks for the quick fix. I can confirm the exception is gone now. However, looking at the code, I am not sure I understand the purpose of the Param_Discrete_Numeric
class. Now (with the code above) I get a warning:
The combinations of discrete features is large at 39. Optimization will proceed very slowly due to the combinatorial explosion. Recommend reducing the number of discrete parameters used.
Which means that my Param_Discrete_Numeric
is treated as a categorical variable by the optimiser. If that's the case, may you please explian what is the difference between it and Param_Categorical
? E.g., how is Param_Categorical("category", ["1", "2"])
different from Param_Discrete_Numeric("num_category", [1,2])
when it comes to surrogate model building and acquisition optimisation? Thanks!
Hi,
Thanks for the nice package.
I am encountering issues when trying to use
Param_Discrete_Numeric
.If I understand the code correctly the idea is to use this as a continuous variable during optimisation and mapping the suggested evaluation values to the closest of the numerical categories (via the
unit_demap
method).However, by the virtue of
Param_Discrete_Numeric
inheriting fromParam_Discrete
this seems to be broken and I get the following exception when trying to useParam_Discrete_Numeric
.