mapillary / mapillary/OpenSfM

How to use opensfm extend_reconstruction command?

Open
#1,063 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
3.8k
Forks
899
PR merge metrics
No merged PRs in 30d

Description

Hey y'all, I've seen this discussed before but I haven't been able to get an answer for my problem. In the NodeODM container I call

bin/opensfm extend_reconstruction /var/www/data/251ce1df-643a-412f-a4e9-13d2c41f71bd/opensfm --input reconstruction.json --output reconstruction2.json

This does create reconstruction2.json, but this output tells me something is definitely wrong:

2024-08-05 00:23:41,750 DEBUG: Ceres Solver Report: Iterations: 39, Initial cost: 2.042603e+04, Final cost: 1.586630e+04, Termination: CONVERGENCE
2024-08-05 00:23:41,963 INFO: Removed outliers: 1080
2024-08-05 00:23:42,109 INFO: -------------------------------------------------------
2024-08-05 00:23:42,921 DEBUG: Ceres Solver Report: Iterations: 5, Initial cost: 1.085035e+04, Final cost: 1.077862e+04, Termination: CONVERGENCE
2024-08-05 00:23:43,119 INFO: Removed outliers: 90

My process is as so:

  • Add ~10 images to the images folder under the project
  • Run command specifying the dataset to be the opensfm folder under the project
  • Same output as shown above, for any number of images added (even with none)

I'm quite sure I am invoking the command incorrectly, so could anybody provide an example or explain what part I'm doing wrong? Thanks!

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the bin/opensfm extend_reconstruction entry point and its command help, then trace how reconstruction.json and the images folder are consumed. No source file or test is named; done would require a verified usage example or clarified documentation explaining the expected inputs and output.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
cli, computer-vision
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
24/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.