You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Why is camera coordinate data passed to SMPLLoss during computing MotionLoss? #51
In SmoothOptimizer and RootOptimizer, I think the joints3d/joints3d_op in SMPLLoss/RootLoss is in the world coordinate system. And the re-projection is performed to get the proj_2d joints from (world -> pixel coordinates).
However, it seems like in MotionLoss, the cam_pred_data is passed into RootLoss:
Whilst I think from the logic in rollout_latent_motion(), it looks like cam_pred_data is actually still in the world coordinate system, and is transformed back from the local coordinate system used in the rollout procedure. I am therefore confused about the name of the variables: Why is this data named cam_pred_data with a comment above saying "must return trans and root orient in camera frame...", while the function name is apply_world2prior? And it doesn't look like camera coordinate system data to me.
I just would like to confirm whether this is a naming issue or I misunderstood it. Thank you!
changed the title [-]Why is camera coordinate system used in MotionLoss?[/-][+]Why is camera coordinate date passed to SMPLLoss during computing MotionLoss?[/+]on Feb 20, 2024
changed the title [-]Why is camera coordinate date passed to SMPLLoss during computing MotionLoss?[/-][+]Why is camera coordinate data passed to SMPLLoss during computing MotionLoss?[/+]on Feb 20, 2024
Activity
[-]Why is camera coordinate system used in MotionLoss?[/-][+]Why is camera coordinate date passed to SMPLLoss during computing MotionLoss?[/+][-]Why is camera coordinate date passed to SMPLLoss during computing MotionLoss?[/-][+]Why is camera coordinate data passed to SMPLLoss during computing MotionLoss?[/+]lishisen01 commentedon Jan 8, 2026
https://people.eecs.berkeley.edu/~jathushan/projects/phalp/3D/head_faces.npy
https://people.eecs.berkeley.edu/~jathushan/projects/phalp/3D/mean_std.npy
https://people.eecs.berkeley.edu/~jathushan/projects/phalp/3D/smpl_mean_params.npz
https://people.eecs.berkeley.edu/~jathushan/projects/phalp/3D/SMPL_to_J19.pkl
https://people.eecs.berkeley.edu/~jathushan/projects/phalp/3D/texture.npz
https://people.eecs.berkeley.edu/~jathushan/projects/phalp/bmap_256.npy
https://people.eecs.berkeley.edu/~jathushan/projects/phalp/fmap_256.npy
https://people.eecs.berkeley.edu/~jathushan/projects/phalp/weights/hmar_v2_weights.pth
https://people.eecs.berkeley.edu/~jathushan/projects/phalp/weights/pose_predictor_40006.ckpt
https://people.eecs.berkeley.edu/~jathushan/projects/phalp/weights/config_40006.yaml
https://people.eecs.berkeley.edu/~jathushan/projects/phalp/ava/ava_labels.pkl
https://people.eecs.berkeley.edu/~jathushan/projects/phalp/ava/ava_class_mappping.pkl
When I was accessing these downloaded files, the links were all broken. Can anyone help me find where I can still find a backup of the files? Or if anyone has saved a backup of this file, could you please share it with me? Thank you so much