Brian McFee

Had to nudge the minimal matplotlib here, which has set off a chain of environment updates and other painful nonsense. Meanwhile, I've also thrown in a workflow step to do...

It appears that my use of `hatch_linewidth` requires matplotlib>=3.10. This is quite a bummer, as I think it looks much better with thick hatches. Here's the default (thin) version:

> I think there are other hatches available that could be used for sus4, like stars etc., but I guess they might look terrible. Another option could be to use...

> in a mir_eval-y way I think we can basically cook down all the relevant metrics to a ranking retrieval interface. E.g., the following example should basically cover it: ```python...

> The question is, whether we can come up with a design which simplifies this, I currently cannot think of one because the initial boilerplate code is so simple itself....

> Are there any tasks other than [#423](https://github.com/mir-evaluation/mir_eval/issues/423) (especially ones we already cover) that require nontrivial collection-level aggregation? If we wanted to move ahead on #346 , that probably would....

Had a chance to test this locally, it's a grab bag. Most failures are indeed due to legend location, and we can fix this by setting the loc explicitly. Segment...

Ok, I think this issue with segments is due to this change: https://matplotlib.org/stable/api/prev_api_changes/api_changes_3.9.0.html#boxplots-now-ignore-masked-data-points - axvspan now creates Rectangle instead of Polygon patches, and for some reason that means they are...

Issue punted upstream to https://github.com/matplotlib/matplotlib/issues/28383

Looks like the fix is merged and will be in the 3.9.1 release.