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

ensure correct prediction types are used when postprocessing #942

Open
topepo opened this issue Sep 18, 2024 · 2 comments
Open

ensure correct prediction types are used when postprocessing #942

topepo opened this issue Sep 18, 2024 · 2 comments
Labels
bug an unexpected problem or unintended behavior

Comments

@topepo
Copy link
Member

topepo commented Sep 18, 2024

tune currently uses the specified metric sets to determine what types of predictions are being made. For example, for a binary classification model, we might only request "class metrics" (e.g. sensitivity, accuracy, etc), tune will not generate probability predictions.

However, some postprocessors require multiple types of predictions. For the above example, we might want to optimize the probability threshold. Even though we are only modifying the class predictions, we need the probability predictions to do so.

So: tune should use the metric set and any postprocessor to determine the required prediction types.

@topepo topepo added the bug an unexpected problem or unintended behavior label Sep 18, 2024
@topepo
Copy link
Member Author

topepo commented Sep 18, 2024

Note that the adjustment objects have elements that list the type of prediction is required

@topepo
Copy link
Member Author

topepo commented Sep 18, 2024

Also, we'll need to take into account the outputs too. For example, calibration uses probability predictions to adjust all classification prediction types. If we do not have hard class prediction columns, and error will occur (although we could change this in probably)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug an unexpected problem or unintended behavior
Projects
None yet
Development

No branches or pull requests

1 participant