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
Due to some untold reason, the "neck" joint that PoseWarper used in training is not the ground truth, but the average of left and right shoulder. This brings down the PoseWarper's results about 23 mAP across PoseTrack2017 and PoseTrack2018 valid sets and test sets. In other words, the "true" accuracy of the PoseWarper would be 23 mAP higher than what they report in their paper.
In your paper, you compare your results with the PoseWarper's "faulty" results. From your code, we can see you correctly use the "neck" ground truth in training. That's probably why your "Head" results are much better across PoseTrack valid and test datasets.
I'm curious, you guys really know nothing about the "neck" problem in PoseWarper?
The text was updated successfully, but these errors were encountered:
Due to some untold reason, the "neck" joint that PoseWarper used in training is not the ground truth, but the average of left and right shoulder. This brings down the PoseWarper's results about 2
3 mAP across PoseTrack2017 and PoseTrack2018 valid sets and test sets. In other words, the "true" accuracy of the PoseWarper would be 23 mAP higher than what they report in their paper.In your paper, you compare your results with the PoseWarper's "faulty" results. From your code, we can see you correctly use the "neck" ground truth in training. That's probably why your "Head" results are much better across PoseTrack valid and test datasets.
I'm curious, you guys really know nothing about the "neck" problem in PoseWarper?
The text was updated successfully, but these errors were encountered: