Skip to content
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

uber calibration groups issue #104

Closed
topepo opened this issue May 8, 2023 · 2 comments · Fixed by #109
Closed

uber calibration groups issue #104

topepo opened this issue May 8, 2023 · 2 comments · Fixed by #109

Comments

@topepo
Copy link
Member

topepo commented May 8, 2023

There are group arguments to the cal_plot_* and cal_estimate_* functions. There are overlaping issues regarding groups (#79, #92,#98, #100). Looking at these, we should have a more systematic approach rather than multiple refactors that might overlap.

I think that we should only enable group-by processing when the input is a data frame (and not an object generated by the tune package). We should default to using .config for tune objects when there are multiple configurations (and NULL otherwise).

Change 1

In the many functions it is set in both the S3 generic and also in an internal helper called tune_results_args().

  • For non-tune S3 generics, allow the user to set it as an argument and validate it in the generic with a helper function.
  • For tune generics, give no group argument and set group to .config if there are multiple configurations.

The logic for group should not be in multiple places so it should be taken out of tune_results_args().

Change 2

The user-facing argument should be called .by to be consistent with new dplyr syntax. It should only accept a single, categorical column in the data.

@topepo topepo changed the title user calibration groups issue uber calibration groups issue May 8, 2023
@EmilHvitfeldt
Copy link
Member

change 3

error if grouped data.frame passed to functions. Refer to .by argument

@github-actions
Copy link

github-actions bot commented Jun 1, 2023

This issue has been automatically locked. If you believe you have found a related problem, please file a new issue (with a reprex: https://reprex.tidyverse.org) and link to this issue.

@github-actions github-actions bot locked and limited conversation to collaborators Jun 1, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants