-
Notifications
You must be signed in to change notification settings - Fork 16
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
How to correctly convert Motion-X dataset to HumanML3D format (n,263)? #98
Comments
I also met the same problem and fixed it adding the following codes to motion_representation.py. It modifies the coordinate system of joints before saving it in new_joints directory.
You can call them as follows:
|
I couldn't explain how excited I am. I will try this code as soon as possible. |
I also found that the face in the data was facing downwards, and after applying a rotation matrix, it seems to be correct:
|
Thank you very much!!!! |
Hi @MD-Student , May I ask which sub-dataset are you converting? thank you. |
As a matter of fact, my dataset structure is also in a mess. The sub-dataset I am converting is located in the kungfu folder. And I am using the smplh model downloaded from its website. |
Thank you for the information, same here XD. |
I have not encountered the promblem of data dim mismatching. Just follow the ipynb scripts. |
Hello, I have uploaded the new version of the Tomato-aligned motion data from Motion-X++ data here, so you could check it, and I show some visualization for you here. |
Thany you very much! I will check it soon. |
Hi @zhangyuhong01, thank you for the new version release! I happened to find that there are some problems with the text annotation for the animation subset. In the Motion-X/texts/animation folder, there are only .npy files instead of .txt files. |
I use tomato_representation/raw_pose_processing,motion_representation and motionx2hummanml/transfer_body_only these three scripts to convert motionx smplx_322 data. The result data is (n,263) but they cannot be visualized correctly.
For example:
The text was updated successfully, but these errors were encountered: