It's not obvious to me whether this is a bug for JAMS or mir_eval, but when evaluating segment data, I got some nasty exceptions whenever the interval data was not ordered.
This is easily fixable by calling annotation.data.sort_values('time', inplace=True) before generating interval/values and calling mir_eval.
It's not obvious to me whether this is a bug for JAMS or mir_eval, but when evaluating segment data, I got some nasty exceptions whenever the interval data was not ordered.
This is easily fixable by calling
annotation.data.sort_values('time', inplace=True)
before generating interval/values and calling mir_eval.[tagging @craffel for insight]