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

Bug in relative pose estimation? #145

Open
MarkYu98 opened this issue Nov 3, 2023 · 1 comment
Open

Bug in relative pose estimation? #145

MarkYu98 opened this issue Nov 3, 2023 · 1 comment

Comments

@MarkYu98
Copy link

MarkYu98 commented Nov 3, 2023

In utils.py L292:

f_mean = np.mean([K0[0, 0], K1[1, 1], K0[0, 0], K1[1, 1]])

f_mean = np.mean([K0[0, 0], K1[1, 1], K0[0, 0], K1[1, 1]])

Shouldn't it be

f_mean = np.mean([K0[0, 0], K0[1, 1], K1[0, 0], K1[1, 1]])?

Though it might not cause any noticeable difference since most cameras have similar fx and fy :)

@zhangsngood
Copy link

Hello! There are also some questions hereabout eatimation issues. I would like to know how the relative extrinsic parameters in ./assets/scannet_test_pairs_with_gt.txt are obtained. If I know the camera pose extrinsics of two images, how is the relative pose extrinsics T_0to1 between these two poses. Does anyone have any idea about it?

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