search

OpenDroneMap / NodeMICMAC

A Lightweight REST API to Access MICMAC Photogrammetry and SFM Engine.
https://opendronemap.org/nodemicmac/
GNU General Public License v3.0
79 stars 21 forks source link

Ran out of storage space #38

Closed kylenessen closed 4 years ago

kylenessen commented 4 years ago

I'm trying to process a linear mission with 722 jpg images, totaling around 5.84 GB. I've let it run without apparent issue for about 148 hours now, and upon checking the Diagnostic page in WebODM, I found that I have used all 173 GB allocated to the docker container. I have no other projects, either in progress or completed, loaded in the container. Returning to the Dashboard, the duration timer has reverted to 87 hours and the Task Output is now blank, leading me to believe the processing failed.

As reference, here are my processing options: ccd-width: 13.2, max-concurrency: 8, multi-scale: true, resize-to: 2048, ccd-height: 8.8

Is this a bug? Or do I need to allocate a lot more space to WebODM?

Thanks!

dronemapper-io commented 4 years ago

You shouldn't have to allocate more space. Try running the job with multi-scale enabled and the resize to 500 pixel. Unless it is a very homogeneous scene, there is not a need to compute tie-points at 2048 pixel. Also, if you just need a good ortho, set the zoom at 4. Tha should speed up processing. Thanks

On Mon, Oct 7, 2019, 4:28 PM kylenessen notifications@github.com wrote:

I'm trying to process a linear mission with 722 jpg images, totaling around 5.84 GB. I've let it run without apparent issue for about 148 hours now, and upon checking the Diagnostic page in WebODM, I found that I have used all 173 GB allocated to the docker container. I have no other projects, either in progress or completed, loaded in the container. Returning to the Dashboard, the duration timer has reverted to 87 hours and the Task Output is now blank, leading me to believe the processing failed.

As reference, here are my processing options: ccd-width: 13.2, max-concurrency: 8, multi-scale: true, resize-to: 2048, ccd-height: 8.8

Is this a bug? Or do I need to allocate a lot more space to WebODM?

Thanks!

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/dronemapper-io/NodeMICMAC/issues/38?email_source=notifications&email_token=ALIJ6KXIGEHOAS6EMEE2LH3QNOSZJA5CNFSM4I6KALMKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HQF3U4Q, or mute the thread https://github.com/notifications/unsubscribe-auth/ALIJ6KQYE2XKEZCBBAI4SQLQNOSZJANCNFSM4I6KALMA .

kylenessen commented 4 years ago

Great, thanks for the feedback.

I was running out of space with nodeODM as well, which makes me think it was some other issue. I have resized my docker disk image, freed up some space on my drive, and will reprocess it based on your recommendations.

Does resizing affect the quality of the ortho? Or is it just for tie-points?

Thanks!

dronemapper-io commented 4 years ago

Yes, it only affects the initial tie-point creation and feature matching. It does really impact the time and size of files created during the first stage of processing (tie-points/features) Thanks

On Tue, Oct 8, 2019 at 1:56 PM kylenessen notifications@github.com wrote:

Great, thanks for the feedback.

I was running out of space with nodeODM as well, which makes me think it was some other issue. I have resized my docker disk image, freed up some space on my drive, and will reprocess it based on your recommendations.

Does resizing affect the quality of the ortho? Or is it just for tie-points?

Thanks!

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/dronemapper-io/NodeMICMAC/issues/38?email_source=notifications&email_token=ALIJ6KXU2HHX4K6JPD66UZ3QNTQWJA5CNFSM4I6KALMKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAVM5OY#issuecomment-539676347, or mute the thread https://github.com/notifications/unsubscribe-auth/ALIJ6KXSRGCOWMG7N7DS3J3QNTQWJANCNFSM4I6KALMA .