This repository has been archived by the owner on Feb 16, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 179
(Potentially) A very important bug in extract_features_from_gt.py #77
Comments
Here is a PyCharm debuging example: [BoxList(num_boxes=2, image_width=800, image_height=1216, mode=xyxy), BoxList(num_boxes=2, image_width=800, image_height=1216, mode=xyxy)] boxes for the 1st BoxList: boxes for the 2nd BoxList: |
Saw someone did mention the same issue in this PR. |
@ZhangHanbo Hi, Do you know how to generate the format of all grounding truth that you mentioned above. |
what I did was simply modifying the extract_features function and saving the ground truth as allimages.npy:
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi, 12-in-1 is a very interesting work based on vilbert.
However, I am confused about the extract_features_from_gt.py scipt.
In the README under data/ directory, you said: to extract data features, users should firstly transform all grounding truth as the following format:
{
{
'file_name': 'name_of_image_file',
'file_path': '<path_to_image_file_on_your_disk>',
'bbox': array([
[ x1, y1, width1, height1],
[ x2, y2, width2, height2],
...
]),
'num_box': 2
},
....
}
However, I notice that in the extract_features_from_gt.py script, you do not recover the xywh to xyxy format, which should cause wrong feature extraction.
I am not sure whether this is an elaborate design or a bug.
Further, if this is a bug, what about the features used in VILBERT and 12-in-1? Are they correctly extracted using the correct bounding boxes?
The text was updated successfully, but these errors were encountered: