-
Notifications
You must be signed in to change notification settings - Fork 402
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IOU type for mean average precision #821
Comments
Hi! thanks for your contribution!, great first issue! |
Could you explain the difference between bbox iou and the segmentation IoU? |
@gianscarpe ^^ |
Hi and thanks for the question! As in pycocotools (the official COCO library for mAP), the difference between the two regards how to compute positive and negative pairs of bounding-box. BBox_IOU computes how much the bounding-boxes overlap, while segmentation-iou evaluates how much the segmentation masks (ground-truth and predicted). Different way to compute intersections and unions :) |
Is it perhaps similar to the Non-Max Suppression? Pages 41-45: |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
PR: #822 |
🚀 Feature
would be nice to have detection.map.MeanAveragePrecision similar to what pycocotools provides. In particular, introduced a parameter "iou_type" in order to choose between "bbox" and "segm" (for instance segmentation).
Motivation
Having a metric for instance segmentation, which is currently unavailable.
Pitch
Instantiate MeanAveragePrecision(..,, iou_type="segm") to evaluate instance segmentation
Alternatives
Additional context
The text was updated successfully, but these errors were encountered: