-
Notifications
You must be signed in to change notification settings - Fork 49
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
[Feature] Add COCO Metric #23
Conversation
Co-authored-by: yancong <[email protected]>
Co-authored-by: yancong <[email protected]>
Kindly ping @RangiLyu have a look |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Co-authored-by: Zaida Zhou <[email protected]>
Co-authored-by: Zaida Zhou <[email protected]>
Co-authored-by: Zaida Zhou <[email protected]>
Co-authored-by: Zaida Zhou <[email protected]>
mmeval/metrics/coco_detection.py
Outdated
iou_thrs (float | List[float], optional): IoU threshold to compute AP | ||
and AR. If not specified, IoUs from 0.5 to 0.95 will be used. | ||
Defaults to None. | ||
classwise_result (bool): Whether to return the computed |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Simply using classwise is fine, eval_classwise or return_classwise might also be OK.
For now, classwise_results does not provide more meaningful information than classwise.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Update all detection classwise_result -> classwise
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Other metrics such as MeanIoU may also need to update
Continue #9
Related PR: open-mmlab/mmdetection#9079
Before refactor:
After refactor:
Not load ann_file:
The area in coco is based on gt_mask. if using gt_bbox, it will lead to different small/medium/large AP results. Moreover, the area calculated from gt_mask area in CocoDetectionMetric is almost equal to coco-json file (still a little difference in small AP). So if only calculate bbox ap, and do not load ann_file, it is suggested to load mask at the same time.
Using gt_box area:
Using gt_mask area:
Load ann_file: