-
Notifications
You must be signed in to change notification settings - Fork 21
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
Relation between kpts_3d_pred and pose #18
Comments
Hi, by default the translation of the input 3D box is used for visualization EgoNet/libs/visualization/egonet_utils.py Line 70 in 13e3758
You can also play with other translation estimation paradigms. For example, use cv2.solvePnP to solve the translation with the predicted 2D keypoints from EgoNet EgoNet/tools/inference_legacy.py Line 501 in 13e3758
|
Great, thanks for the answer! |
Hello,
Thank you for open-sourcing this amazing project!
I have a question about the convention for the transformation of the 3D box. EgoNet only produces an egocentric pose (i.e. camera coordinates) corresponding to the rotation between the 3D box extracted from the keypoints and a template 3D box. We also have a translation corresponding to the first point in kpts_3D_pred, here.
To better understand the coordinate systems involved I'm doing the following experiment:
After doing these two steps, I still need one translation to place the 3D box in space (in the camera system). The question is, what translation should I use? Is it the one corresponding to the first point in kpts_3d_pred?
Thank you for your time
The text was updated successfully, but these errors were encountered: