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
, this codebase performs pose tracking by matching bboxes & associated poses between frames based on a weighted sum of various distance metrics elaborated from object- and keypoint-level bbox IoUs as well as the shared ORB features contained within these bboxes.
) depending on whether the boxes in b) were from frame t or not? It seems like the ORB-based matching criteria are given weight 0 for b) boxes from frame t and 1 otherwise.
The text was updated successfully, but these errors were encountered:
From my understanding of
PoseFlow/utils.py
Line 157 in 4d2a78d
It also seems like the bitartite matching graph is between a) all bboxes in frame t+1 and b) the most recent bboxes associated with each of the object tracks discovered thus far ( in frames <= t) based on https://github.com/MVIG-SJTU/AlphaPose/blob/9dafbb2259a36bf92df87042863eba7f543d3cf9/PoseFlow/utils.py#L93.
I was wondering why these distance metrics are weighted differently (
PoseFlow/tracker-general.py
Line 112 in 4d2a78d
The text was updated successfully, but these errors were encountered: