-
Notifications
You must be signed in to change notification settings - Fork 40
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
ModuleNotFoundError: No module named 'psbody.smpl.fast_derivatives.smpl_derivatives' #19
Comments
Hi @Jgorin! I tried to reproduce this error by setting up an environment and copying the content of the |
I'm having this exact same problem, and I'm 100% sure I put it in the correct |
I finally found the problem (and a potential solution). The install instructions here are problematic: Lines 38 to 43 in 1e3bf3c
The problem doing this is that the folder structure ends up like:
Python can't find The solution is to paste the
|
After copy psbody into the site-packages directory, follow the instruction at https://github.com/MPI-IS/mesh to setup the package.
It'll be solve the 'ModuleNotFoundError', merging psbody.mesh into psbody. |
Hello,
Thanks so much for sharing this work! I get an error when trying to run mosh on labelled data:
I verified that the psbody package is placed in the site-packages folder, and I can import psbody, but if I import psbody.smpl I get the same error.
I also was attempting to run the code for labelling unlabelled c3d files and was getting an OmegcaConf resolver error for resolve_mocap_subject(the same as here #8). Tracing through the soma and moshpp code, it looks like there isn’t a resolver set for resolve_mocap_subject, but it looks like resolve_mocap_session defined on line 164 of run_tools in moshpp (https://github.com/nghorbani/moshpp/blob/6599a2d7dde7baab67ef9d859c967c14c4e7badc/src/moshpp/tools/run_tools.py#L125) does what resolve_mocap_subject should do.
I also had the exact same issue as described here #16 and fixed in the exact same manner which seems to work.
The text was updated successfully, but these errors were encountered: