Dataset has been split into 0 submodels. Reconstructing each submodel

I’m encountering an error after matching about which I can’t find any information. Image matching seems to work fine (matched 7383 pairs), then i get:
[WARNING] Submodels directory already exist at: /code/submodels
followed by:
[INFO] Dataset has been split into 0 submodels. Reconstructing each submodel…

The rest of the steps run and fail because there’s no data to process:
[INFO] Aligning submodels…
[INFO] Finished split stage
[INFO] Running merge stage
[WARNING] No input point cloud files to process
[INFO] Merging all crop bounds: []
[WARNING] No bounds found for any submodel.
[WARNING] No orthophoto/cutline pairs were found in any of the submodels. No orthophoto will be generated.
[INFO] Merging 0 shots.geojson files
[INFO] Finished merge stage
[INFO] Running odm_postprocess stage
[INFO] Post Processing
[INFO] Finished odm_postprocess stage
[INFO] No more stages to run

I have WebODM installed and running on Docker (MacOS), and I’m using the command line to run the following:

docker run -it --rm
-v “$(pwd)/images:/code/images”
-v “$(pwd)/odm_georeferencing:/code/odm_georeferencing”
-v “$(pwd)/odm_meshing:/code/odm_meshing”
-v “$(pwd)/odm_orthophoto:/code/odm_orthophoto”
-v “$(pwd)/odm_texturing:/code/odm_texturing”
-v “$(pwd)/opensfm:/code/opensfm”
-v “$(pwd)/smvs:/code/smvs”
-v “$(pwd)/submodels:/code/submodels”
opendronemap/odm --skip-3dmodel --fast-orthophoto --ignore-gsd --orthophoto-resolution 2 --verbose --texturing-data-term area --split 400

I’m processing 779 images, so attempting to split them roughly into two sets with split-merge.

Any help much appreciated!

1 Like

Welcome!

Can you tell us a bit more about your Mac and whether or not this is the most recent version of WebODM?

Also, have you had this analysis crash before?

Thanks Saijin.

It’s a 2019 Macbook Pro (Intel) with 2.4GHz 8 Core i9, 64GB RAM, running MacOS Ventura (13.1), Docker 4.16.2 (95914), and WebODM 1.9.19.

I start up docker, then run WebODM in one terminal window (webodm.sh start), then run my task in another terminal window using the code I pasted above.

I haven’t encountered this issue before.

1 Like

What do your Resource Allocation settings look like for Docker?

You might be having issues with disk space and or RAM.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.