kapture icon indicating copy to clipboard operation
kapture copied to clipboard

matches-vs-inliers and F/E matrices

Open ducha-aiki opened this issue 3 years ago • 3 comments

Hi,

Is there any way to store both tentative matches (which can be wrong) and inliers (after RANSAC, but not yet sure 3D observations)? And, related to this - is there a plan for storing intermediate pairwise image relationships, like essental/findamental matrices? I can prepare a PR for this.

Best, Dmytro

ducha-aiki avatar May 04 '21 13:05 ducha-aiki

Hi, for matches, what you call inliers is what we call matches with geometric verification in kapture-localization. There is no way to have both tentative matches and inliers within the same kapture but what we do is to have one kapture with the tentative matches and one with the inliers. In practice, we store all the matches in an 'orphan' folder, detached from kapture, and the kapture folders are built with symlinks. see https://github.com/naver/kapture-localization/blob/1.1_draft/doc/tutorial.adoc#recommended-dataset-structure

For intermediate pairwise image relationships (essental/findamental matrices), we have no intention of adding them to the format right now.

-- Yohann

yocabon avatar May 06 '21 12:05 yocabon

Hi,

Thank you for the quick answer. I will try to do the thing with two kaptures for tentative matches.

Regarding F/E, I hope that you will reconsider at some point. For example, of the use-cases I have in mind is to use kapture as The format for the 3d reconstruction, e.g for this our paper https://arxiv.org/abs/2011.11986

Without F/E relations, one cannot use kapture as a representation for SfM system (so that SfM system is build around kapture format). Then one has to mix it with other, handcoded formats, which kind of defy idea of the kapture as universal format.

ducha-aiki avatar May 06 '21 12:05 ducha-aiki

Hi!

Thanks for the question and comment. At the moment, we use kapture mainly for visual localization and we added reconstruction data that is often used in such algorithms. However, we are currently considering adding something a bit more generic that could be used to store F/E matrices or other algorithms specific data. If you start using kapture for your own SfM pipeline, you could save such additional data in your own format. To be complaint with kapture data (e.g. for the datasets you use), you just need to use the same timestamps and sensor ids in your format.

Best, Martin

humenbergerm avatar May 18 '21 06:05 humenbergerm

Issue seem resolved. Please reopen if needed.

jujumo avatar Mar 28 '23 13:03 jujumo