You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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)
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.
The text was updated successfully, but these errors were encountered: