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
I think it would be beneficial to factor out the eval_op, eval_end, eval_reduce API so that others who want to define custom metrics (like #95) can extend the already optimized evaluate that is built off of them. Not sure how this would interact with UnionMetrics.
The text was updated successfully, but these errors were encountered:
@bhgomes Could it be that this is resolved by #163? Depending on what you want to define, PreMetric, SemiMetric or Metric, you can subtype your custom metric to Union[Pre/Semi]Metric, overload those functions that are not covered by the generic fallbacks, and otherwise let the package do its job. See #151 (comment) for an example.
I think it would be beneficial to factor out the
eval_op
,eval_end
,eval_reduce
API so that others who want to define custom metrics (like #95) can extend the already optimizedevaluate
that is built off of them. Not sure how this would interact withUnionMetrics
.The text was updated successfully, but these errors were encountered: