Instance Segmentation Confusion Matrix
Description
Solves for https://github.com/roboflow/supervision/issues/238
Type of change
Please delete options that are not relevant.
- [ ] Bug fix (non-breaking change which fixes an issue)
- [x] New feature (non-breaking change which adds functionality)
- [ ] This change requires a documentation update
How has this change been tested, please provide a testcase or example of how you tested the change?
Please use this colab for testing: https://colab.research.google.com/drive/1OKjyH8JmFMROJ97447DUn13p-GDP6dXl Test cases have been added
Hi @mayankagarwals 👋🏻! Is that code ready for review? It is still marked as draft.
Hey @SkalskiP. No, the code is still not complete as I'm waiting for your input on https://github.com/roboflow/supervision/issues/238. There are two different ways we can design the API.
@mayankagarwals okey I'm rolling that PR over to supervision-0.14.0
Hi @kirilllzaitsev @hardikdava @SkalskiP
While the code here is functional, I wanted to ask your opinion on force_masks
Right now I'm assuming if force_masks is passed we will enforce that every detection in the from_detections is accompanied by a mask.
The segmentation confusion matrix is computed only when force_masks is passed
@mayankagarwals hey, this PR should be relevant. force_masks=True refers to the case when the masks are enforced, while if force_masks=False, but the masks are present in annotations ('segmentation' field), they will be parsed since now
hi @kirilllzaitsev!
Cool! I guess then it makes sense to provide a segmentation matrix only if force_masks = true.
@kirilllzaitsev @hardikdava Before I wrap up the documentation and tests, can you please go through the PR and let me know if you have any queries or concerns?
@SkalskiP @hardikdava PR is ready for review. Have added a colab link for testing.