-
Notifications
You must be signed in to change notification settings - Fork 161
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
[CLIFF] misc questions for evaluation #178
Comments
1 a). We used the COCO17 keypoint configuration. |
Thank you for your clarifications on the first and the second questions! For the third one, I have a follow-up question. Does it mean that the checkpoint uploaded on Google Drive will show the MPJPE of 47.6 and PA-MPJPE of 32.7? |
Yes, you are right. |
@yohanshin Hi! Sorry to bother you. I'm trying to reproduce the result on Human3.6M with the released model |
Hi @RammusLeo , I actually could not get the table for Human3.6M dataset. Sorry for not being so helpful.. |
Thank you all the same for your response! I'll try other methods. |
hi @RammusLeo ,i got the same result as yours,I feel confused |
are these numbers?@RammusLeo |
Dear Authors,
Hi, I am trying to reproduce the evaluation table and have a few questions.
I could get similar (not exactly the same though) PA-MPJPE for 3DPW dataset using HR48 backbone. But I want to be confirmed if I am doing it correctly
-- From the previous Issue post, I found that you are using the bbox obtained through projecting 3D keypoints onto image plane. In this case, which keypoints configuration did you use (e.g., COCO17, OpenPose25, H36M ...)
-- I am using the camera focal length as a known value and computed it by averaging the x and y focal lengths. Is it same as what you've done?
Is the HR48 checkpoint uploaded in Google Drive the same as what you got for the Human36M evaluation performance?
Thank you so much for your answer in advance!
The text was updated successfully, but these errors were encountered: