OpenDroneMap / OpenDroneMap/ODM
Possible bug in --align: should rerun always rerun align?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6.5k
- Forks
- 1.3k
- Avg merge
- 5d 6h
- Merged PRs (30d)
- 4
Description
If I rerun a completed project that uses --align as follows:
docker run --rm -v /super-secret-dataset-location:/datasets opendronemap/odm --project-path /datasets dataset-name --dem-resolution 4 --orthophoto-cutline --orthophoto-resolution 4 --rolling-shutter --sfm-no-partial --max-concurrency 5 --dsm --rerun-from odm_postprocess
the process correctly identifies all the stages as run and completes after the check. If I rerun with out specifying the --rerun-from as in the following example, it will rerun from odm_georeferencing.
docker run --rm -v /seventb/freetown:/datasets opendronemap/odm --project-path /datasets WJ_034-backup --dem-resolution 4 --orthophoto-cutline --orthophoto-resolution 4 --rolling-shutter --sfm-no-partial --max-concurrency 5 --dsm --rerun-from odm_postprocess
I'm not sure if this is the expected behavior. It is not the usual behavior for a stage to rerun if it doesn't need to.
I suspect any dataset will replicate, including Brighton Beach:
https://github.com/pierotofy/drone_dataset_brighton_beach/tree/master
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
Reproduce the two Docker commands from the issue, including the Brighton Beach dataset if available, and compare stage selection with and without --rerun-from. Trace the CLI logic that decides whether odm_georeferencing and later stages need rerunning; done when the expected --align behavior is established and the observed rerun decision is corrected or documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, python
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100