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 joint order #4

Closed
MengHao666 opened this issue Aug 9, 2020 · 5 comments
Closed

about the joint order #4

MengHao666 opened this issue Aug 9, 2020 · 5 comments

Comments

@MengHao666
Copy link

MengHao666 commented Aug 9, 2020

First,thank u for such great work!
Now I have been confused about the joint order in the dataset.
In the ho3d_v2 dataset, you mention the joint order is different from that of MANO model.
And now I take part in the competetion Ho3d_v2 Codalab competition u provide, and I get the reults which have high error in joint loacation but much lower mesh error.
So I wonder if the joint order in the evaluation dataset is also different from that of original MANO model?
Hope you could provide some suggestion,thank u!

@shreyashampali
Copy link
Owner

hi,
The joint orderings follow the MANO model ordering even for the evaluation set as mentioned here. Could you please point me to the place where it is mentioned that the joint order is different from MANO model?

@MengHao666
Copy link
Author

MengHao666 commented Aug 9, 2020

Thanks for the quick reply.
I'm sorry to confuse the code of jointsMapManoToSimple u provided and that of hassony's self.reorder_idxs.They may change the oreder to adapt to the differentiable Mano layer they proposed.

In my own understanding , u use jointsMapManoToSimple only for simple visualization ? Is that true?

Thanks u again!

@MengHao666
Copy link
Author

Another question is that whether the order of samples in train.txt has been carefully shuffled to ensure uniform distribution.
Hope to get your suggestions, thanks!

@shreyashampali
Copy link
Owner

yes, jointsMapManoToSimple is only for visualization.
The samples in train.txt are just randomly shuffled. It does not guarantee uniform distribution

@MengHao666
Copy link
Author

Ok,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

2 participants