You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have seen the issue in #606, and I agree that the processing method of VG is the same as stated in #606 (comment). However, this processing method does not work for RefCOCO, following is an image in RefCOCO processed by expand2square:
And the following is the same image without processing by expand2square:
It seems that the second one is correct.
So I wonder if the processing methods used in RefCOCO and VG are different.
The text was updated successfully, but these errors were encountered:
Hi, I still haven't got it; the normalized [xa, ya, xb, yb] seems correct for VG data after padding, but is not correct for coco data after padding, right?
Hi, I still haven't got it; the normalized [xa, ya, xb, yb] seems correct for VG data after padding, but is not correct for coco data after padding, right?
Is it true? I also haven't get whether the normalized coordinates in llava665k are adjusted for padding or not
Question
I have seen the issue in #606, and I agree that the processing method of VG is the same as stated in #606 (comment). However, this processing method does not work for RefCOCO, following is an image in RefCOCO processed by expand2square:
And the following is the same image without processing by expand2square:
It seems that the second one is correct.
So I wonder if the processing methods used in RefCOCO and VG are different.
The text was updated successfully, but these errors were encountered: