asking for an advice about merging two reconstructions
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3.8k
- Forks
- 899
- PR merge metrics
- No merged PRs in 30d
Description
First of all, thanks @paulinus for sharing your great work!
May I ask your advice for an use case?
Let's say I have a linear dataset of 500 images (taken from a driving car). I was able to reconstruct them in an incremental manner (i.e., adding one view, triangulating it, doing bundle, and repeating.). However, it currently takes almost 4-5 hours. (Although computation time does not matter much for now, it takes too much. From an earlier discussion (#130), I learned that there are local_bundle_radius or bundle_interval options.)
Do you think if I can reconstruct once for a subset 1 of (earlier) 250 images and once for a subset 2 of (later) 250 images, and nicely merge them? Between their boundary, how can I calculate relative {R, T} (e.g., between the last camera of subset 1, and the first camera of subset 2).
Alternatively, do you think if I can subdivide the set such as [0-251] and [250-500] (with overlap), figure out the relative {R, T} between 250th and 251th, and apply it to all the second subset? (what if a scale is different?)
Would there be a better way to do it when using your library? Could you provide some pseudocodes/logics/hint for that?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the existing local_bundle_radius and bundle_interval options and the earlier discussion in issue #130. The issue does not name files or tests; determine whether the library supports merging independently reconstructed subsets, handling relative poses and scale, and document a supported workflow or identify the missing capability.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- opencv, python
- Domain
- computer-vision
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100