Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

convert new_joints to new_joint_vecs #152

Open
UsanoCoCr opened this issue Sep 24, 2024 · 6 comments
Open

convert new_joints to new_joint_vecs #152

UsanoCoCr opened this issue Sep 24, 2024 · 6 comments

Comments

@UsanoCoCr
Copy link

I want to mathematically convert new_joints to new_joint_vecs, I look at the code in motion_representation.ipynb I'm not sure if new_joints_vecs to new_joints is reversible, has anyone done the same thing?

@Gelercatty
Copy link

i also concern about this problem, i saw someone do it like this, but im not sure if this is correct. it seems they use process_file() to
transform new_joints[time,22,3] into new_ joints_feature(vector) [time,263] directly, but joints and new_joints is different..?
image
https://github.com/OpenMotionLab/MotionGPT/blob/main/mGPT/data/HumanML3D.py line 88

@NinomiyaAsuka
Copy link

i also concern about this problem, i saw someone do it like this, but im not sure if this is correct. it seems they use process_file() to transform new_joints[time,22,3] into new_ joints_feature(vector) [time,263] directly, but joints and new_joints is different..? image https://github.com/OpenMotionLab/MotionGPT/blob/main/mGPT/data/HumanML3D.py line 88

I also face this problem... Can I ask if you have sloved how to convert new_joints to new_joint_vecs?

@Jatinkalal
Copy link

Hey as anyone been able to solve this problem?

@tinelion
Copy link

i also concern about this problem, i saw someone do it like this, but im not sure if this is correct. it seems they use process_file() to transform new_joints[time,22,3] into new_ joints_feature(vector) [time,263] directly, but joints and new_joints is different..? image https://github.com/OpenMotionLab/MotionGPT/blob/main/mGPT/data/HumanML3D.py line 88

no, the code copied from HumanML3D, it's just the same.

@Gelercatty
Copy link

i also concern about this problem, i saw someone do it like this, but im not sure if this is correct. it seems they use process_file() to transform new_joints[time,22,3] into new_ joints_feature(vector) [time,263] directly, but joints and new_joints is different..? image https://github.com/OpenMotionLab/MotionGPT/blob/main/mGPT/data/HumanML3D.py line 88

no, the code copied from HumanML3D, it's just the same.

thanks a lot!

@Gelercatty
Copy link

i also concern about this problem, i saw someone do it like this, but im not sure if this is correct. it seems they use process_file() to transform new_joints[time,22,3] into new_ joints_feature(vector) [time,263] directly, but joints and new_joints is different..? image https://github.com/OpenMotionLab/MotionGPT/blob/main/mGPT/data/HumanML3D.py line 88

I also face this problem... Can I ask if you have sloved how to convert new_joints to new_joint_vecs?

just use this function!

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants