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

some tips(advice) to better performance and UV-map performance #42

Open
GuodongQi opened this issue Aug 8, 2019 · 3 comments
Open

some tips(advice) to better performance and UV-map performance #42

GuodongQi opened this issue Aug 8, 2019 · 3 comments

Comments

@GuodongQi
Copy link

GuodongQi commented Aug 8, 2019

Hello, i have tried your code and make some changes(tips) to perform better. Hope it would help:

  1. L1 loss weight . The L1 loss weight generated is wrong accrodding to your code and your uv-map-template after dilation. UV map shouldnot be dilated
  2. TV loss. I added tv loss with corrected weights. The TV loss weights should smaller than L1 loss two order of magnitudes . The results showed it improved a little.
  3. From UV map to Verts. changed SAMPLE algorithm little.
  4. Increase joints-center verts loss weight.

However,the MPJPE-PA i calculated is about 62, much lager than the paper listed.
The MPJPE-PA between joints from UV-map-generated-form-gt3d and gt3ds is about 22mm, it also much larger than paper listed.

@tszhang97
Copy link

@GuodongQi would you like to share your modified code? And how to calculate the 3D joint? SMPL fitting or just multiple the joint regressor?

@GuodongQi
Copy link
Author

@willie1997 I am afraid not. The latter,just multiple the joint regressor.

@Lotayou
Copy link
Owner

Lotayou commented Aug 23, 2019

@GuodongQi Thanks for the tips. Do you care to make a pull request?
Also I think it's perfectly normal for my implemetation to be worse than the paper reported, since I only used 1/100 of the h36m dataset (i.e. about 30K frames). If you have access to the full human36m data you can train a much better model.

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

3 participants