Build51 problems

Almost every dataset I try to process with Build 51 fails, often with a similar error.
Knowing basically nothing of programming (forgotten what little I did know a few decades ago!), I’ve been looking through the console log to see if I could figure it out. Saijin_Naib’s suggestion of a race condition was along the lines of what I had been thinking, but so far solutions have not been found.

Having a 3rd go at a set of 1320 images today I noticed this in the console log

FileNotFoundError: [Errno 2] No such file or directory: ‘E:\WebODM51\resources\app\apps\NodeODM\data\aa8db589-4604-4e2f-afad-6a228ee667a7\opensfm\features\DJI_0828.JPG.features.npz’

DJI_0828.JPG is one of the images in the set, but there appears to be a gap in
\reports\features - files DJI_0800 - 0834.JPG.json are absent

Also in \opensfm\features files DJI_0801 - 0834.features.npz are absent (one less missing file)

They are listed in \opensfm\exif

They are listed in \opensfm\image_list.txt

Hopefully this is useful information that will help solve the problem!

2 Likes

Piero and I are just discussing this, but it looks like maybe a pipe size limitation that sometimes Python can hit:

As far as I know, this isn’t confirmed, but this seems to be the direction Piero is researching currently.

2 Likes

Tried again, but another fail with quite a few missing image .npz and .json files.

Trying again with no resizing and Ultra quality so that GPU isn’t used for feature extraction, hopefully it’s a way around this problem. It will take a lot longer, but otherwise I guess it means going back to build 47 to get tasks to complete.

1 Like

It seems that build 51 just wont process this subset of 1320 images, GPU fails as posted above. Going full size ultra to use the CPU for feature extraction appeared to be going well, until it crashed after nearly 84 hours. End of the console below, but this appears to be the problem:

No proper input scene descriptor given.

[INFO] Finished odm_filterpoints stage
[INFO] Running odm_meshing stage
[INFO] Writing ODM Mesh file in: E:\WebODM51\resources\app\apps\NodeODM\data\8c1c07a8-5f4f-4624-9014-289c7ac900d6\odm_meshing\odm_mesh.ply
[INFO] running “E:\WebODM51\resources\app\apps\ODM\SuperBuild\install\bin\PoissonRecon” --in “E:\WebODM51\resources\app\apps\NodeODM\data\8c1c07a8-5f4f-4624-9014-289c7ac900d6\odm_filterpoints\point_cloud.ply” --out “E:\WebODM51\resources\app\apps\NodeODM\data\8c1c07a8-5f4f-4624-9014-289c7ac900d6\odm_meshing\odm_mesh.dirty.ply” --depth 11 --pointWeight 4.0 --samplesPerNode 1.0 --threads 15 --bType 2 --linearFit
[INFO] running “E:\WebODM51\resources\app\apps\ODM\SuperBuild\install\bin\OpenMVS\ReconstructMesh” -i “E:\WebODM51\resources\app\apps\NodeODM\data\8c1c07a8-5f4f-4624-9014-289c7ac900d6\odm_meshing\odm_mesh.dirty.ply” -o “E:\WebODM51\resources\app\apps\NodeODM\data\8c1c07a8-5f4f-4624-9014-289c7ac900d6\odm_meshing\odm_mesh.ply” --remove-spikes 0 --remove-spurious 20 --smooth 0 --target-face-num 400000 -v 0
[INFO] Finished odm_meshing stage
[INFO] Running mvs_texturing stage
[INFO] Writing MVS Textured file in: E:\WebODM51\resources\app\apps\NodeODM\data\8c1c07a8-5f4f-4624-9014-289c7ac900d6\odm_texturing\odm_textured_model_geo.obj
[INFO] running “E:\WebODM51\resources\app\apps\ODM\SuperBuild\install\bin\texrecon” “E:\WebODM51\resources\app\apps\NodeODM\data\8c1c07a8-5f4f-4624-9014-289c7ac900d6\opensfm\undistorted/reconstruction.nvm” “E:\WebODM51\resources\app\apps\NodeODM\data\8c1c07a8-5f4f-4624-9014-289c7ac900d6\odm_meshing\odm_mesh.ply” “E:\WebODM51\resources\app\apps\NodeODM\data\8c1c07a8-5f4f-4624-9014-289c7ac900d6\odm_texturing\odm_textured_model_geo” -d area -o gauss_clamping -t none --no_intermediate_results --max_texture_size=8192
E:\WebODM51\resources\app\apps\ODM\SuperBuild\install\bin\texrecon (built on Jan 13 2022, 18:56:48)
Load and prepare mesh:
Reading PLY: 180085 verts… 360211 faces… done.
Generating texture views:
No proper input scene descriptor given.
A input descriptor can be:
BUNDLE_FILE - a bundle file (currently onle .nvm files are supported)
SCENE_FOLDER - a folder containing images and .cam files
MVE_SCENE::EMBEDDING - a mve scene and embedding

===== Dumping Info for Geeks (developers need this to fix bugs) =====
Child returned 1
Traceback (most recent call last):
File “E:\WebODM51\resources\app\apps\ODM\stages\odm_app.py”, line 94, in execute
self.first_stage.run()
File “E:\WebODM51\resources\app\apps\ODM\opendm\types.py”, line 346, in run
self.next_stage.run(outputs)
File “E:\WebODM51\resources\app\apps\ODM\opendm\types.py”, line 346, in run
self.next_stage.run(outputs)
File “E:\WebODM51\resources\app\apps\ODM\opendm\types.py”, line 346, in run
self.next_stage.run(outputs)
[Previous line repeated 4 more times]
File “E:\WebODM51\resources\app\apps\ODM\opendm\types.py”, line 327, in run
self.process(self.args, outputs)
File “E:\WebODM51\resources\app\apps\ODM\stages\mvstex.py”, line 117, in process
system.run(’"{bin}" “{nvm_file}” “{model}” “{out_dir}” ’
File “E:\WebODM51\resources\app\apps\ODM\opendm\system.py”, line 106, in run
raise SubprocessException(“Child returned {}”.format(retcode), retcode)
opendm.system.SubprocessException: Child returned 1

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

[ERROR] Uh oh! Processing stopped because of strange values in the reconstruction. This is often a sign that the input data has some issues or the software cannot deal with it. Have you followed best practices for data acquisition? See Flying Tips — OpenDroneMap 2.7.1 documentation

1 Like

This set of 1320 full size images has finished processing successfully with build 47 in 44h 51m.
Options: auto-boundary: true, dem-resolution: 2.0, dsm: true, dtm: true, gps-accuracy: 10, matcher-neighbors: 10, min-num-features: 11000, orthophoto-resolution: 2.0, pc-quality: high, pc-rectify: true, use-3dmesh: true
Average GSD: 2.58 cm
Area: 1,412,709.04 m²
Reconstructed Points: 254,379,191

1 Like

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