Tool crashes when yolo is selected about review_object_detection_metrics HOT 2 CLOSED

Hi @Kraufel,

Thank you for reporting this issue. I have already fixed the problem you mentioned.

Regarding your second question, to make it clearer, I also changed the names of some the formats of the "detection in the interface". So, please update the files with these changes.

Find below the explanation why if you use your coordinates, it wont work.

Considering your groundtruth:
0 0.1466346153846154 0.4230769230769231 0.09134615384615384 0.08173076923076923

These coordinates are in YOLO's format: <class_id> <x_center> <y_center> <width> <height> (RELATIVE)

And your detection: 0 0.74 0.271635 0.153846 0.687500 0.427885 is in the format: <class_id> <confidence> <x_center> <y_center> <width> <height> (RELATIVE)

If you take a look at the paper (page 6), you will note that YOLO's coordinates are represented in the format:

As the coordinates are normalized by the image's resolution, you have to inform the directory with the images, so the program can retrieve the width and height of the image to calcualte the coordinates of the bounding boxes.

If the groundtruths and detections above belong to the image 2007_000549.jpg, whose width and height are 375 and 500 respectively, their absolute coordinates in the format x, y, x2, y2 will be:

Groundtruth: (38, 191, 72, 232)
Detection: (-27, -30, 231, 184)

See that the x and y coordinates of the detections are negative, which means this detection cannot belong to this image.

I don't know where you got that detected bounding box, but it cannot belong to the image 2007_000549 in the toyexample.

I hope it helps. Let me know if you were able to run the program with your files.

Best regards,
Rafael

from review_object_detection_metrics.

As no activity has been performed in this issue, I decided to close it.

If anyone decides to add any comment or have doubts on this topic, feel free to reopen the issue.

from review_object_detection_metrics.