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

About the evaluation of H36M #138

Open
XiaobenLi00 opened this issue Aug 23, 2023 · 0 comments
Open

About the evaluation of H36M #138

XiaobenLi00 opened this issue Aug 23, 2023 · 0 comments

Comments

@XiaobenLi00
Copy link

XiaobenLi00 commented Aug 23, 2023

I notice that in the code, only 14 joints used for eval on h36m, why not 17 joints?

# Joint selectors
# Indices to get the 14 LSP joints from the 17 H36M joints
H36M_TO_J17 = [6, 5, 4, 1, 2, 3, 16, 15, 14, 11, 12, 13, 8, 10, 0, 7, 9]
H36M_TO_J14 = H36M_TO_J17[:14]
# Indices to get the 14 LSP joints from the ground truth joints
J24_TO_J17 = [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 18, 14, 16, 17]
J24_TO_J14 = J24_TO_J17[:14]

joint_mapper_h36m = constants.H36M_TO_J17 if dataset_name == 'mpi-inf-3dhp' else constants.H36M_TO_J14
joint_mapper_gt = constants.J24_TO_J17 if dataset_name == 'mpi-inf-3dhp' else constants.J24_TO_J14

Does that mean only for mpi-inf-3dhp, 17 joints are used while 14 joints are used for joints? Why eval in this way?

By the way, I also notice that in ProHMR (in this file prohmr/configs/datasets.yaml ), the keypoints lists are different for different protocols on h36m, I am a little confused, could you give me any information?

Why there is a config named `H36M-VAL-P2-OPENPOSE', what dose that mean?

Thanks a lot.

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

1 participant