-
-
Notifications
You must be signed in to change notification settings - Fork 404
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
Irace tuning doesn't work with dependencies #369
Comments
Well it DOES work. 2 hints:
Well the answer seems to be you simple need to exchange "expression" with "qoute"? Close? Improve docs? Suggestion? |
Well the problem is that the definition of the learner param sets in the mlr source uses |
Hmm, ok I need to check this. This relates to this here: We dont really use the "requires" in the learner params inside of the learner definitions, except for sanity checking of inputs. But I will check this later |
On a related note, I wasn't able to get any tuning to work with the parameter sets defined in the learner (i.e. |
Yes, but this is very clear. The sets in the learners define the whole possible space. You are supposed to write down the feasible region yourself for the optimizer. But @kerschke is therefore supposed to define default tuning par sets for the learners in gsoc. Which would allow EXACTLY what you tried to do. |
Great, looking forward to that. |
i have added checks now that ensure that "expression" is neither used in the learner$param.set nor the tuning param.set. |
added unit tests for RLearners and tuning |
replace expression with quote in parameter requirements (fixes #369)
Tuning with irace gives an error when the parameter sets have dependencies as defined in the learners, e.g.
gives me
Looking at the unit tests for Irace, dependencies are specified with
quote()
instead ofexpression()
-- onlyexpression()
is used in the definition of the learners.The text was updated successfully, but these errors were encountered: