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 have provided a list of tuples of integers, e.g. [(0,), (1, 2), (2, 3, 4)] as the choices argument of trial.suggest_categorical method.
The optimization session seems working while generating a number of (one for each choice?) warning as the title of this issue.
My question is that, what's the drawback I have to be aware of from the warning? Some possibilities I think of are, from worst:
it seems running, but the resulting FrozenTrial instances may have wrong results.
the result of optimization can be suboptimal.
the performance of optimization can be suboptimal.
I can't run this on multiple processes (with DB as storage).
nothing, because tuple of ints are actually allowed.
nothing, even when values of other types is provided.
The text was updated successfully, but these errors were encountered:
Hello @majiang, I think your optimization basically works without any problem.
You can use Optuna with the search space in parallel, and with RDB.
Some types such as tuple or dictionary are not recommended because there is no guarantee for compatibility across different storage backends (e.g. MySQL and Redis).
Not all types are guaranteed to be compatible with all storages. It is recommended to restrict the types of the choices to None, bool, int, float, and str.
I have provided a list of tuples of integers, e.g.
[(0,), (1, 2), (2, 3, 4)]
as thechoices
argument oftrial.suggest_categorical
method.The optimization session seems working while generating a number of (one for each choice?) warning as the title of this issue.
My question is that, what's the drawback I have to be aware of from the warning? Some possibilities I think of are, from worst:
FrozenTrial
instances may have wrong results.The text was updated successfully, but these errors were encountered: