-
Notifications
You must be signed in to change notification settings - Fork 65
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
Multiple types of keypoints and descriptors #8
Comments
Hi Dmytro! Thanks for your interest in this. Indeed, we already discussed a lot how to support multiple types of local features. We will continue the discussion and get back to you as soon as possible. Best, |
Thank you, Martin! If possible, I would be happy to join the discussion :) |
Great! It would also be helpful if you could share some more details about your needs. At the moment we use kapture with multiple features, but not within the same reconstruction. |
Sure. The general idea is to revisit MODS, which combines the multiple type of features in order to speed-up matching of the easy pairs and to allow matching the hard pairs, where any single feature fails, but combined they work. https://github.com/ducha-aiki/mods-light-zmq |
Hi, There are no changes to the "sensor" part of the format. What do you think of these changes ? |
Hi, It fits my use-case, thank you!
where the metric is "L2" for the most and "Hamming" for the binary features, for example. |
Hi,
I am trying to fit the kapture for my use case, which requires multiple types of local features, both detectors and descriptors, e.g. SuperPoint, R2D2, SIFT+HardNet.
The current kapture format assumes a single type of local feature -- which is hardcoded in the filenames "keypoints.txt", "descriptors.txt". If I would make a fork for support multiple feature types, would it be merged at some point, or do you not plan to change the format?
Best, Dmytro.
The text was updated successfully, but these errors were encountered: