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

Why the homography matrix all elements are equal to ones? #66

Open
Abbsalehi opened this issue Jun 25, 2024 · 1 comment
Open

Why the homography matrix all elements are equal to ones? #66

Abbsalehi opened this issue Jun 25, 2024 · 1 comment

Comments

@Abbsalehi
Copy link

Abbsalehi commented Jun 25, 2024

I read database.db using pycolmap, but when I form two_view_geometry using two image ids, the homography matrix all elements equal to ones.

reconstruction= pycolmap.Database(database_path)
two_view_geometry= reconstruction.read_two_view_geometry(1, 2)
H = two_view_geometry.H
@Abbsalehi Abbsalehi changed the title Why the homography matrix all elements are equal to one? Why the homography matrix all elements are equal to ones? Jun 25, 2024
@franioli
Copy link
Collaborator

franioli commented Jun 30, 2024

Hi, did you use pycolamp (or COLMAP from the GUI) to run the reconstruction or did you just run the matching with DIM?
At the moment, DIM does not write either the H, F, or E matrixes in the two_view_geometry table, but by default, it fills the keypoints and matches tables.
Additionally, if a geometric verification (e.g., with pydegensac) is run, we also store the inliers matches in the two_view_geometry table, but we currently do not store the F matrix (this can be introduced in the next release).
Anyway, if you run a reconstruction with pycolmap or from the GUI, then the F and E matrixes in the two_view_geometry table are estimated and stored in the database as usual.

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