Bounding box cross image border #182

New Issue

2020-12-26T03:15:05+01:00

lilong-epfl commented

2020-12-26 03:15:05 +01:00

(Migrated from github.com)

I noticed that sometimes the output bbox cross the image border. I run yolov4 coco model "yolo4_fp16_416_b4.rt". My video frame is 1920x1080, the output has the format <cl, xmin, ymin, xmax, ymax, prob> and get the following result:

Another example:
62 1076.07 905.269 1432.92 1078.23 0.781482
0 1258.91 758.674 1764.24 1088.5 0.877903
0 269.656 904.954 839.898 1081.5 0.827466
0 -7.8483 761.261 171.499 1085.89 0.812028

Any ideas?

I noticed that sometimes the output bbox cross the image border. I run yolov4 coco model "yolo4_fp16_416_b4.rt". My video frame is 1920x1080, the output has the format <cl, xmin, ymin, xmax, ymax, prob> and get the following result: ![image](https://user-images.githubusercontent.com/13543618/103144338-e89e7d00-4762-11eb-98f6-191f1eec2003.png) Another example: 62 1076.07 905.269 1432.92 1078.23 0.781482 0 1258.91 758.674 1764.24 1088.5 0.877903 0 269.656 904.954 839.898 1081.5 0.827466 0 -7.8483 761.261 171.499 1085.89 0.812028 Any ideas?

mive93 commented

2021-01-04 16:07:00 +01:00

(Migrated from github.com)

It's probabily do to how the box is computed (https://github.com/ceccocats/tkDNN/blob/master/src/Yolo.cpp#L65) and the fact that there are no checks on the image bound. However, it shouldn't be a problem.

Fetulhak commented

2021-08-05 17:37:29 +02:00

(Migrated from github.com)

I noticed that sometimes the output bbox cross the image border. I run yolov4 coco model "yolo4_fp16_416_b4.rt". My video frame is 1920x1080, the output has the format <cl, xmin, ymin, xmax, ymax, prob> and get the following result:

Another example:
62 1076.07 905.269 1432.92 1078.23 0.781482
0 1258.91 758.674 1764.24 1088.5 0.877903
0 269.656 904.954 839.898 1081.5 0.827466
0 -7.8483 761.261 171.499 1085.89 0.812028

Any ideas?

Hi @lilong-epfl @mive93 @AlexeyAB I have got into the same problem is there any fix on the source code to solve this issue? I think the problem is when yolov4 predict the relative coordinates it did not check whether it is out of image border IDK?

[0.00623968 0.77162105 0.01684078 0.01875179 0. 0.08409741] this is an output prediction for my input image of size 832. when I did the calculations on the extended version of the original image center_X becomes around 5.19 while the width of the bbox is around 14.01 which will be out of the image border.

> I noticed that sometimes the output bbox cross the image border. I run yolov4 coco model "yolo4_fp16_416_b4.rt". My video frame is 1920x1080, the output has the format <cl, xmin, ymin, xmax, ymax, prob> and get the following result: > ![image](https://user-images.githubusercontent.com/13543618/103144338-e89e7d00-4762-11eb-98f6-191f1eec2003.png) > > Another example: > 62 1076.07 905.269 1432.92 1078.23 0.781482 > 0 1258.91 758.674 1764.24 1088.5 0.877903 > 0 269.656 904.954 839.898 1081.5 0.827466 > 0 -7.8483 761.261 171.499 1085.89 0.812028 > > Any ideas? Hi @lilong-epfl @mive93 @AlexeyAB I have got into the same problem is there any fix on the source code to solve this issue? I think the problem is when yolov4 predict the relative coordinates it did not check whether it is out of image border IDK? [0.00623968 0.77162105 0.01684078 0.01875179 0. 0.08409741] this is an output prediction for my input image of size 832. when I did the calculations on the extended version of the original image center_X becomes around 5.19 while the width of the bbox is around 14.01 which will be out of the image border.

This repo is archived. You cannot comment on issues.

1 Participants

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: mmr/tkDNN#182