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
In some use-cases we have boundaries as list of points like [0, 10, 21, 55, 365] (peak positions, breakpoints, etc.), to make mir_eval.segment applicable we have to turn those points into intervals. But one can notice, that some of the evaluation methods actually convert intervals back to boundaries.
I suppose, that would be convenient to have api allowing users to avoid unnecessary conversions.
The text was updated successfully, but these errors were encountered:
In some use-cases we have boundaries as list of points like [0, 10, 21, 55, 365] (peak positions, breakpoints, etc.), to make mir_eval.segment applicable we have to turn those points into intervals. But one can notice, that some of the evaluation methods actually convert intervals back to boundaries.
I suppose, that would be convenient to have api allowing users to avoid unnecessary conversions.
The text was updated successfully, but these errors were encountered: