facebookresearch / facebookresearch/co3d

Generating camera poses using Colmap

Open
#83 0 comments 1 reaction 0 assignees View on GitHub
Dominant language
Python
Stars
1.2k
Forks
87
PR merge metrics
No merged PRs in 30d

Description

Hello, your dataset is fantastic! Currently, I am using Colmap software to simulate the process of generating camera poses similar to yours. However, the results obtained from the same set of images differ significantly from the camera poses you provided, and these differences persist even after coordinate transformations. I have tried multiple sets of images, and the results are consistent. I'm not sure what is causing these differences. There are many parameters to set during feature extraction, feature matching, or sparse reconstruction, and I have used the default settings for all of these parameters. How should I configure them?
The image below shows a visual comparison of the pose results generated from the "TeddyBear624_103316_207474" set—the green poses are from my Colmap-generated raw data, the yellow poses are after I performed the coordinate transformation from Colmap to PyTorch3D, and the red poses are yours. The teddybear point cloud below is from my Colmap results, and the one above is from yours. As you can see, there is a significant difference. I look forward to your guidance!
![capture_20240202101321638](https://github.com/facebookresearch/co3d/assets/155620558/c9757f03-e0e0-4271-b229-198ee92e921c)
![capture_20240202101334747](https://github.com/facebookresearch/co3d/assets/155620558/5630e001-58bf-429c-8a29-fb9a058e8de5)

![capture_20240202101351462](https://github.com/facebookresearch/co3d/assets/155620558/204d5d07-61bd-40b9-a33d-410d6820cc04)

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the COLMAP feature extraction, feature matching, and sparse reconstruction workflow on the “TeddyBear624_103316_207474” image set using the default parameters described in the issue. Compare the resulting raw and PyTorch3D-transformed poses and point cloud with the provided poses; done means identifying a reproducible configuration or coordinate-transformation difference that explains the mismatch.

Written by the indexing model from the issue text.

Assessment

Domain
computer-vision
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.