Skip to content
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

how does the to3d func work? #4

Closed
longbowzhang opened this issue Jun 23, 2020 · 1 comment
Closed

how does the to3d func work? #4

longbowzhang opened this issue Jun 23, 2020 · 1 comment

Comments

@longbowzhang
Copy link

Hi, thanks for sharing the great work.
I have a question about heatmap. I noticed that you encode the distance of the joints to the camera cam_dist = np.sqrt(joint.x3d ** 2 + joint.y3d ** 2 + joint.z3d ** 2) , why not simply encode the z-depth value of the joints joint.z3d? any particular reason?

Besides, could you elaborate a little bit on

LoCO/utils.py

Line 97 in 7ebaca7

def to3d(x2d, y2d, cam_dist, fx, fy, cx, cy):
, basically what does this k value mean?

LoCO/utils.py

Line 113 in 8371ef0

k = (-1) * np.sqrt(

@fabbrimatteo
Copy link
Owner

Hi @longbowzhang,

Thank you for your interest in our work.

You are right, it is much simpler to encode the z-depth value directly. In fact we used this approach for Panoptic and Human3.6 as described in the paper's supplementary material.

As for the to3d function, it has been obtained by solving the following system w.r.t. the 3D coordinates:

k is just a recurrent coefficient calculated one time and used to obtain each 3D coordinate.

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

No branches or pull requests

2 participants