move methods for tunable()
from tune to parsnip
#606
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is part of moving methods for
tunable()
from tune to the package which holds the corresponding object class:recipe
,step
, andcheck
are already in recipes, that PR just cleans up the documentation. Clean up (internal) documentation oftunable()
methods recipes#856model_spec
and various model types such aslinear_reg
etc are moved to parsnip (aka this PR here)workflow
is moved to workflows move method fortunable()
from tune to workflows workflows#130When methods have been moved, the methods are registered conditionally on the version of tune from which they have been removed. The tune PR is tidymodels/tune#433
The tests require multiple packages so they are all in extratests: tidymodels/extratests#34
The PR on extratests should be merged first, then the ones on recipes and parsnip, then workflows, then tune.
This is part of the wider aim of introducing
extract_parameter_dials()
andextract_parameter_set_dials()
and the next steps are:extract_parameter_set_dials()
extract_parameter_dials()
parameters()
similar to this PR set