WebODM - SubModel Creation Error - OSError: [WinError 1] Incorrect function:

vdmj · October 19, 2024, 7:36am

I am running Win 11 and fail to create submodels. The WebODM is setup on external Sandisk Extreme Pro 1 TB drive.

A set of 1476 photos runs without issue when not using split-merge, even with both feature quality and pc quality at high.

However, when set to split the dataset (tried 100, 300, 500 and 1000 with overlap = 150 and 0m) it is always failing after generating the submodel folders with no photos in it.

Read out python error
OSError: [WinError 1] Incorrect function: ‘F:\WebODM\resources\app\apps\NodeODM\data\df3664fa-9528-4bce-9aa4-3941f10910f6\images\DJI_000A(4).JPG’ → ‘F:\WebODM\resources\app\apps\NodeODM\data\df3664fa-9528-4bce-9aa4-3941f10910f6*\opensfm..*\submodels\submodel_0000\images\DJI_000A(4).JPG’

This seems to be relating to python (error “[WinError 1] Incorrect function:” seems to be a common python error), however, is the path string command correct?

Strange path string, why is “openfsm” and “…” part of the path string? Should the path string not be

'F:\WebODM\resources\app\apps\NodeODM\data\df3664fa-9528-4bce-9aa4-3941f10910f6\submodels\submodel_0000\images\DJI_000A(4).JPG'

without

\opensfm\..

smathermather · October 19, 2024, 5:42pm

What’s the format type of the drive? I’m thinking the links are failing. OpenSfM doesn’t copy the data into the subdirectories, but symlinks them. Windows supports symlinks, but not all drive formats do.

Saijin_Naib · October 20, 2024, 5:07am

Only NTFS does, and not over network-mounted volumes.

ExFAT/FAT32, et al do not.

vdmj · October 20, 2024, 9:38am

Thank you, format is exFAT

vdmj · October 20, 2024, 9:38am

Thank you, as per reply above, format is exFAT

smathermather · October 20, 2024, 5:18pm

Thanks for the confirmation. Linking to the github issue so they are connected:

github.com/OpenDroneMap/ODM

Split-merge fails creating submodels in server

opened 07:39AM - 19 Jul 19 UTC

x-ancin

software fault enhancement

### How did you install OpenDroneMap? (Docker, natively, ...)? Using Docker i…n a linux server ### What's your browser and operating system? (Copy/paste the output of https://www.whatismybrowser.com/) Command line via PuTTy ### What is the problem? When I run ODM in a local machine it works fine with and without splitting the dataset, using > docker run -it --rm -v G:/test:/datasets/code opendronemap/odm --project-path /datasets or > docker run -it --rm -v G:/test:/datasets/code opendronemap/odm --project-path /datasets --split 10 --split-overlap 3 As long as I have the data in a local folder (either hard drive or USB external disk), it does everything as expected But when I run it on the server, it works only **without** the split command: >docker run -it --rm -v /my-server/Project folder:/datasets/code opendronemap/odm --project-path /datasets Works fine, but as soon as I add > --split 10 --split-overlap 3 to the code, I get the following error: >[INFO] running /code/SuperBuild/src/opensfm/bin/opensfm create_submodels >/var/www/data/44a86e01-7ff1-4848-a6b6-711097026c96/opensfm >Traceback (most recent call last): >File “/code/SuperBuild/src/opensfm/bin/opensfm”, line 34, in >command.run(args) >File “/code/SuperBuild/src/opensfm/opensfm/commands/create_submodels.py”, line 37, in run >meta_data.load_clusters_with_neighbors()) >File “/code/SuperBuild/src/opensfm/opensfm/large/metadataset.py”, line 154, in >create_submodels >os.symlink(src_relpath, dst) >OSError: [Errno 95] Operation not supported >Traceback (most recent call last): >File “/code/run.py”, line 56, in >app.execute() >File “/code/stages/odm_app.py”, line 93, in execute >self.first_stage.run() >File “/code/opendm/types.py”, line 376, in run >self.next_stage.run(outputs) >File “/code/opendm/types.py”, line 357, in run >self.process(self.args, outputs) >File “/code/stages/splitmerge.py”, line 65, in process >octx.run(“create_submodels”) >File “/code/opendm/osfm.py”, line 21, in run >(context.opensfm_path, command, self.opensfm_project_path)) >File “/code/opendm/system.py”, line 76, in run >raise Exception(“Child returned {}”.format(retcode)) >Exception: Child returned 1 It seems like it opensfm has problems read/writing the submodels folder. I am added to the docker user group, but I do not have sudo rights when I run the command. ### What should be the expected behavior? If this is a feature request, please describe in detail the changes you think should be made to the code, citing files and lines where changes should be made, if possible. The expected behavior is that ODM creates the submodel folders, and processes the dataset in chunks, so then I can extract each submodel's orthophoto and DSM to work with smaller tif files afterward ### How can we reproduce this? (What steps did you do to trigger the problem? What parameters are you using for processing? If possible please include a copy of your dataset uploaded on Google Drive or Dropbox. Be detailed) Run ODM with --split on a server disk

We’d definitely welcome a pull request that warns Windows users when using file systems that don’t support split merge.

Barring that, a pull request adding a warning in the split-merge documentation would help as well:

github.com

OpenDroneMap/docs/blob/publish/source/large.rst

.. large

Splitting Large Datasets
========================

Starting with ODM version ``0.6.0`` you can split up very large datasets into manageable chunks (called submodels), running the pipeline on each chunk, and then producing merged DEMs, orthophotos and point clouds. The process is referred to as "split-merge".

Why might you use the split-merge pipeline? If you have a very large number of images in your dataset, split-merge will help make the processing more manageable on a large machine (it will require less memory). If you have many machines all connected to the same network you can also process the submodels in parallel, thus allowing for horizontal scaling and processing thousands of images more quickly.

Split-merge works in WebODM out of the box as long as the processing nodes support split-merge, by enabling the ``--split`` option when creating a new task.

Calibrate images
----------------

Image calibration is recommended (but not required) for large datasets because error propagation due to image distortion could cause a bowl effect on the models. Calibration instructions can be found at 	`Camera Calibration </tutorials/#calibrating-the-camera>`_.

.. figure:: images/msimbasi_bowling.png
   :alt: image of lens distortion effect on bowling of data
   :align: center

This file has been truncated. show original

The workaround in the meantime is to backup and reformat or transfer to a drive that supports symlinks.

vdmj · October 24, 2024, 9:32am

Thank you for considering updating the help files.

To confirm, have formatted drive to NTFS and first round of large split (750 photos) did not complain, also still running a small split (300 photos) on ultra settings, but seems to successfully process split-merge. Will follow up with confirmation on result.

smathermather · October 24, 2024, 11:37am

Excellent. Thanks for the update. Looking forward to seeing if we’ve got you sorted.

vdmj · October 24, 2024, 5:10pm

Now there is something else related to memory.

1476 photos, split size 300, overlap 50, pc-quality ultra and errors, no photo resizing

[INFO] running “F:\WebODM\resources\app\apps\ODM\SuperBuild\install\bin\OpenMVS\DensifyPointCloud” “F:\WebODM\resources\app\apps\NodeODM\data\44c6364a-2a85-4722-8846-d89578fce176\submodels\submodel_0000\opensfm\undistorted\openmvs\scene.mvs” --resolution-level 1 --dense-config-file “F:\WebODM\resources\app\apps\NodeODM\data\44c6364a-2a85-4722-8846-d89578fce176\submodels\submodel_0000\opensfm\undistorted\openmvs\Densify.ini” --max-resolution 5472 --max-threads 12 --number-views-fuse 2 --sub-resolution-levels 2 --archive-type 3 -w “F:\WebODM\resources\app\apps\NodeODM\data\44c6364a-2a85-4722-8846-d89578fce176\submodels\submodel_0000\opensfm\undistorted\openmvs\depthmaps” -v 0 --cuda-device -1
[WARNING] OpenMVS ran out of memory, we’re going to turn on tiling to see if we can process this.
[INFO] running “F:\WebODM\resources\app\apps\ODM\SuperBuild\install\bin\OpenMVS\DensifyPointCloud” “F:\WebODM\resources\app\apps\NodeODM\data\44c6364a-2a85-4722-8846-d89578fce176\submodels\submodel_0000\opensfm\undistorted\openmvs\scene.mvs” --resolution-level 1 --dense-config-file “F:\WebODM\resources\app\apps\NodeODM\data\44c6364a-2a85-4722-8846-d89578fce176\submodels\submodel_0000\opensfm\undistorted\openmvs\Densify.ini” --max-resolution 5472 --max-threads 12 --number-views-fuse 2 --sub-resolution-levels 2 --archive-type 3 -w “F:\WebODM\resources\app\apps\NodeODM\data\44c6364a-2a85-4722-8846-d89578fce176\submodels\submodel_0000\opensfm\undistorted\openmvs\depthmaps” -v 0 --fusion-mode 1 --cuda-device -1
[INFO] Computing sub-scenes
[INFO] running “F:\WebODM\resources\app\apps\ODM\SuperBuild\install\bin\OpenMVS\DensifyPointCloud” “F:\WebODM\resources\app\apps\NodeODM\data\44c6364a-2a85-4722-8846-d89578fce176\submodels\submodel_0000\opensfm\undistorted\openmvs\scene.mvs” --sub-scene-area 660000 --max-threads 12 -w “F:\WebODM\resources\app\apps\NodeODM\data\44c6364a-2a85-4722-8846-d89578fce176\submodels\submodel_0000\opensfm\undistorted\openmvs\depthmaps” -v 0 --cuda-device -1

===== Dumping Info for Geeks (developers need this to fix bugs) =====
Child returned 3221225725
Traceback (most recent call last):
File “F:\WebODM\resources\app\apps\ODM\stages\odm_app.py”, line 82, in execute
self.first_stage.run()
File “F:\WebODM\resources\app\apps\ODM\opendm\types.py”, line 470, in run
self.next_stage.run(outputs)
File “F:\WebODM\resources\app\apps\ODM\opendm\types.py”, line 470, in run
self.next_stage.run(outputs)
File “F:\WebODM\resources\app\apps\ODM\opendm\types.py”, line 470, in run
self.next_stage.run(outputs)
[Previous line repeated 1 more time]
File “F:\WebODM\resources\app\apps\ODM\opendm\types.py”, line 449, in run
self.process(self.args, outputs)
File “F:\WebODM\resources\app\apps\ODM\stages\openmvs.py”, line 138, in process
system.run(‘“%s” “%s” %s’ % (context.omvs_densify_path,
File “F:\WebODM\resources\app\apps\ODM\opendm\system.py”, line 112, in run
raise SubprocessException(“Child returned {}”.format(retcode), retcode)
opendm.system.SubprocessException: Child returned 3221225725

===== Done, human-readable information to follow… =====

[ERROR] The program exited with a strange error code. Please report it at https://community.opendronemap.org

===== Dumping Info for Geeks (developers need this to fix bugs) =====
Child returned 4294967295
Traceback (most recent call last):
File “F:\WebODM\resources\app\apps\ODM\stages\odm_app.py”, line 82, in execute
self.first_stage.run()
File “F:\WebODM\resources\app\apps\ODM\opendm\types.py”, line 470, in run
self.next_stage.run(outputs)
File “F:\WebODM\resources\app\apps\ODM\opendm\types.py”, line 449, in run
self.process(self.args, outputs)
File “F:\WebODM\resources\app\apps\ODM\stages\splitmerge.py”, line 193, in process
system.run(" ".join(map(double_quote, map(str, argv))), env_vars=os.environ.copy())
File “F:\WebODM\resources\app\apps\ODM\opendm\system.py”, line 112, in run
raise SubprocessException(“Child returned {}”.format(retcode), retcode)
opendm.system.SubprocessException: Child returned 4294967295

===== Done, human-readable information to follow… =====

[ERROR] The program exited with a strange error code. Please report it at https://community.opendronemap.org

system · November 23, 2024, 5:11pm

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