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
Note: could be considered as a bug, if it is expected to already allow this behavior otherwise can be seen as a new feature (though a raised exception before the implementation could be useful)
Feature description
Allow to use several time the same metric with different parameters, e.g. Recall@10 + Recall@20.
Right now it does not work as the metric name does not take into account the parameters.
Metrics that could be updated:
FBetaScoreMetric
HammingScore
PrecisionMetric
RecallMetric
TopKAccuracyMetric
... (may have missed some other)
Feature motivation
For simple use cases, deciding on the performance of a model with a single metric or different metrics is feasible. In my case I can accept to have a worse Recall@5 if the Recall@10 is much better. So I need to decide on both metrics.
Note: could be considered as a bug, if it is expected to already allow this behavior otherwise can be seen as a new feature (though a raised exception before the implementation could be useful)
Feature description
Allow to use several time the same metric with different parameters, e.g. Recall@10 + Recall@20.
Right now it does not work as the metric name does not take into account the parameters.
Metrics that could be updated:
Feature motivation
For simple use cases, deciding on the performance of a model with a single metric or different metrics is feasible. In my case I can accept to have a worse Recall@5 if the Recall@10 is much better. So I need to decide on both metrics.
(Optional) Suggest a Solution
Current:
Potential solution:
Config
does not implementDebug
so it probably should be added unless there are reasons not to.The text was updated successfully, but these errors were encountered: