Skip to content
This repository has been archived by the owner on Oct 31, 2023. It is now read-only.

Dimension of full_bodies2.npy doesn't match description #13

Open
wubowen416 opened this issue Sep 5, 2022 · 0 comments
Open

Dimension of full_bodies2.npy doesn't match description #13

wubowen416 opened this issue Sep 5, 2022 · 0 comments

Comments

@wubowen416
Copy link

wubowen416 commented Sep 5, 2022

Hi,

I found that the downloaded full_bodies2.npy has dimension of (N,T,120), which is different from the description for downloading, where it says it should be (N,T,36). Then I noticed that in your data preprocessing code, ARMS_ONLY joints are being selected to 6 joints thus the dimension becomes 36.

p0_windows = np.reshape(p0_windows, (B,T,-1,6))
p0_windows = p0_windows[:,:,ARMS_ONLY,:]
p0_windows = np.reshape(p0_windows, (B,T,-1))

I assume that loading from npy file and indexing using ARMS_ONLY should work. However, I'm not sure if this procedure is correct due to the mismatch between the downloaded file and your description. Could you provide some details regarding this? Thanks in advance.

Another question is that, is full_bodies2.npy corresponding to MTC's output? Should I look for reference in MTC repo in order to understand which joint the value in full_bodies2.npy and full_hands2.npy corresponds to? Looking forward to your reply!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant