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
Currently a metric must return a float in order to be properly logged to MLflow. I suggest that we had the possibility that a metric returns a dict with float as values. Typically to save confusion matrices, per class accuracy etc...
For a given metric called my_metric, we would log it using the metric name and the keys of the returned dict as my_metric/submetricA.
Also as it is not clearly said that the metrics need to return floats (or dict of floats), we could have a proper error handling.
The text was updated successfully, but these errors were encountered:
Currently a metric must return a float in order to be properly logged to MLflow. I suggest that we had the possibility that a metric returns a dict with
float
as values. Typically to save confusion matrices, per class accuracy etc...For a given metric called
my_metric
, we would log it using the metric name and the keys of the returned dict asmy_metric/submetricA
.Also as it is not clearly said that the metrics need to return floats (or dict of floats), we could have a proper error handling.
The text was updated successfully, but these errors were encountered: