I updated the webodm 2 days ago with ODM 2.1.1 and I have a problem trying to process a medium size project with 328 images. It gets to the final step but hasn’t seemed to complete.
Resolution 2D: 128 * 128 = 16,384
Resolution 3D: 128 * 128 * 128 = 2,097,152
Maximum node size: 65,536
Minimum node size: 16,384
Cache size: 64
Adding 0 - odm_georeferencing/odm_georeferenced_model.laz
Pushes complete - joining...
and that is where is just sits and hasn’t seemed to complete. it took aprox 3 hrs to get this point then has run for almost 24 hrs since without finishing.
Welcome! I hope we can get you up & running smoothly here soon.
Could you please provide further information about your processing environment, similar to how I’ve provided it here?
Linux webodm 4.15.0-123-generic #126-Ubuntu SMP Wed Oct 21 09:40:11 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
WebODM via Docker
|Max Images Limit
Options: resize-to: 2736, min-num-features: 24000, feature-quality: ultra, depthmap-resolution: 1368, use-hybrid-bundle-adjustment: true, use-3dmesh: true, mesh-size: 600000, mesh-octree-depth: 12, texturing-nadir-weight: 32, dtm: true, dsm: true, dem-resolution: 3, orthophoto-resolution: 2
Could you provide information about RAM, storage, processor, etc.?
I7 4770 32Gig of ram 2TB drive
I’m going to bet that you ran out of RAM. If you’re fortunate, the process is still running via SWAP/paging, and might just take a very long time, if it didn’t get OOM’d.
I’ve been running out with similar specs (32GB, i7-6700k, 500gb drive) with lower mesh-size during the meshing phase.
What is the resolution of the imagery you’re processing?
5472x3648 is the original size
under diagnostics it shows it using 3.8 gig of ram atm. I can try lowering the settings and see how it turns out.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.