-
-
Notifications
You must be signed in to change notification settings - Fork 14
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
Categorical parameter does not work #90
Comments
Maybe it needs to be specified as categorical like here? Line 112 in c9931ed
|
Could also be that there is a bug regarding categoricals. I will check it tomorrow. "TimeManager": "Categorical([legacy, smooth])"
or
"TimeManager": "Categorical(['legacy', 'smooth'])" |
Thanks, tried it now,
Before this simple test configuration with just one tuning parameter, I also tried tuning some categorical parameters (two possible text values) and some number parameters together in a multiparameter tune. Then it seemed to work and set the categorical parameters correctly. However, if I paused it, and then resumed, it seemed like it wanted to prune some data (or "reduce_ranges") and stopped with an error doing so. Just tried to do a similar test:
|
That message is helpful and it appears that |
Should it even process something called "reduce_ranges"? I did not change any settings or ranges before resuming. |
Description
Experiment with categorical UCI parameter. The tuner tries to set it to a real number instead of one of specified texts.
What I Did
Test6.json:
The text was updated successfully, but these errors were encountered: