Closed Dipankar1997161 closed 1 year ago
@chingswy My second question is:
In Mocap.py for motion capture, There is an option for --opt_exp and --opt_data What all is allowed to pass in that?
Actually I saw the generated cfg_exp.yml file and it is loading body25 , is it possible to load h36m config instead?
If so what command should I pass?
Always these limbs are initialized:
Loss functions:
- limb : 1000.0, Limb of: [8,1],[2,5],[2,3],[5,6],[3,4],[6,7],[2,3],[5,6],[3,4],[6,7],[2,3],[5,6],[3,4],[6,7],[1,0],[9,12],[9,10],[10,11],[12,13],[13,14]
Current command
python apps/demo/mocap.py ${data} --work mv1p --subs 1 2 3 4 --mode smplh-3d-mp --disable_vismesh
Hello @chingswy,
So, I was testing the mv1p.py and trying to generate smpl from the groundtruth keypoints.
These joint idx are given in the h36m files. I am using h36m [ 17 ] ground-truth 2D keypoints, The detection was correct and I received the repro folder. But the repro-smpl and smpl were wrong
COMMAND USED
Detection
Repro smpl
SMPL Mesh
But while optimizing the Joints I got the following error:
I think this is because, 17 H36m keypoints to Body25 is not possible directly. Am I right? that's why the 2d detection is accurate but the smpl conversion is not. Body25 is based on Openpose I suppose, which is Coco17 to 25 joints. Also mapping of openpose and human3.6 joints are different too.
I tried the same on Mocap.py but the same error appeared.
https://github.com/zju3dv/EasyMocap/blob/b44fa3c90b6bbdb3b3fece87fc891cbf154c99f8/easymocap/dataset/config.py#LL626C1-L649C19
Can you tell me what should I do here, in order to avoid this issue? Or is it not possible in Easymocap except if we use Hrnet or Openpose to detect the joints? Since the J regressor used here is body25 based
What if I use human3.6 j regressor in place of body25 one. Will that provide any output difference? I have the H36m j regressor from VIBE and SPIN J_regressor_h36m and j_regressor_extra
What changes in case thats possible would be helpful to know.
Kindly let me know @chingswy
Thank you