Skip to content

Registering tunable() information from an extension package? #826

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

Open
hfrick opened this issue Oct 5, 2022 · 0 comments
Open

Registering tunable() information from an extension package? #826

hfrick opened this issue Oct 5, 2022 · 0 comments
Labels
upkeep maintenance, infrastructure, and similar

Comments

@hfrick
Copy link
Member

hfrick commented Oct 5, 2022

To make engine arguments tunable, we currently modify the tunable() method for the corresponding model type to include a call to parsnip:::add_engine_parameters() with the info on how to match the arguments with dials objects.

More and more engines live in parsnip extension packages and making their args tunable thus requires changes to parsnip. It would be helpful if that info could be provided via the extension package without needing to modify parsnip.

parsnip already carries a "database" in form of various tibbles with fundamental information about the models which gets modified by extension packages by calls to set_engine() etc. Can the same idea be applied to the tunable information?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
upkeep maintenance, infrastructure, and similar
Projects
None yet
Development

No branches or pull requests

2 participants