Skip to content
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

Unable to evaluate bbox #246

Open
yebuxiu123 opened this issue Oct 4, 2023 · 1 comment
Open

Unable to evaluate bbox #246

yebuxiu123 opened this issue Oct 4, 2023 · 1 comment

Comments

@yebuxiu123
Copy link

yebuxiu123 commented Oct 4, 2023

Solo doesn't support bbox metrics for evaluating models? Why am I running
python tools/test_ins.py configs/solo/solo_r50_fpn_8gpu_1x.py SOLO_R50_1x.pth --show --out results_solo.pkl --eval bbox
The following error occurs:
Traceback (most recent call last):
File "tools/test_ins.py", line 257, in
main()
File "tools/test_ins.py", line 235, in main
coco_eval(result_files, eval_types, dataset.coco)
File "/media/gc/My Passport/SOLO/mmdet/core/evaluation/coco_utils.py", line 36, in coco_eval
result_file = result_files[res_type]
KeyError: 'bbox'

@zai1318
Copy link

zai1318 commented Nov 27, 2023

The error you're encountering is related to the mismatch between the type of evaluation metric you're trying to use (bbox for bounding box evaluation) and the capabilities of the SOLO (Segmenting Objects by Locations) model.

SOLO is a framework designed for instance segmentation, not for object detection. The key difference here is:

Instance Segmentation: This task involves identifying each object instance in an image and delineating its shape at the pixel level. Instance segmentation models output masks for each object instance.
Object Detection: This involves locating objects in an image and identifying their classes. Object detection models typically output bounding boxes and class labels.

The error message KeyError: 'bbox' indicates that the evaluation script is expecting results related to bounding boxes (bbox), but the SOLO model generates segmentation masks, not bounding boxes. This mismatch leads to the script not finding the required bbox results in the output of the SOLO model.

To resolve this, you should evaluate your model using metrics appropriate for instance segmentation. Common metrics include Intersection over Union (IoU) or metrics specific to the COCO dataset like Average Precision (AP) for segmentation masks. The evaluation command should be adjusted to reflect these metrics, likely replacing --eval bbox with a parameter suitable for segmentation evaluation, such as --eval segm.

If you specifically need to evaluate object detection performance (bounding box metrics), you would need to use an object detection framework like Faster R-CNN, YOLO, or SSD, which are designed to output bounding boxes for object detection tasks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants