Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The comparison with PoseWarper might not be fair. #32

Open
ArchNew opened this issue Mar 11, 2022 · 1 comment
Open

The comparison with PoseWarper might not be fair. #32

ArchNew opened this issue Mar 11, 2022 · 1 comment

Comments

@ArchNew
Copy link

ArchNew commented Mar 11, 2022

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?

@chenrxi
Copy link

chenrxi commented Apr 28, 2022

it's true.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants