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
Here is how I read this: k1 is the number of labelled keypoints for the person, x0 is to the left of the bounding box, x1 to the right and similarly for y0,y1 above and below.
Now if k1==0 i.e. we do not have any annotated keypoints for a person object then dx will be non-zero if and only if the predicted keypoint lies to the left of x0 or to the right of x1 or in other words if it lies significantly outside the persons tight bounding box. Similarly for dy. Filtering of the exponents for visible keypoints the nis also skipped when k1==1.
In particular if I am reading this correctly this means anything within vague proximity of the bounding box is considered "a perfect match", regardless of where around there it is. Sort of like a "well it correctly realised there is a person somewhere around here, can't blame it if it got the keypoints completely wrong". It feels like I must be missing something here, please do correct me if that is the case!
The text was updated successfully, but these errors were encountered:
I am struggling to see the reasoning in dealing with person objects without keypoint annotations in the OKS computation:
cocoapi/PythonAPI/pycocotools/cocoeval.py
Lines 212 to 232 in 8c9bcc3
Here is how I read this:
k1
is the number of labelled keypoints for the person,x0
is to the left of the bounding box,x1
to the right and similarly fory0,y1
above and below.Now if
k1==0
i.e. we do not have any annotated keypoints for a person object thendx
will be non-zero if and only if the predicted keypoint lies to the left ofx0
or to the right ofx1
or in other words if it lies significantly outside the persons tight bounding box. Similarly fordy
. Filtering of the exponents for visible keypoints the nis also skipped whenk1==1
.In particular if I am reading this correctly this means anything within vague proximity of the bounding box is considered "a perfect match", regardless of where around there it is. Sort of like a "well it correctly realised there is a person somewhere around here, can't blame it if it got the keypoints completely wrong". It feels like I must be missing something here, please do correct me if that is the case!
The text was updated successfully, but these errors were encountered: