Task failure, another case of "No proper input scene descriptor given"

[Gordon]

33 hours into an attempt to create a 3D model of a landslip, the task has failed.
I’ve seen this same error a few times, but have no idea what causes it. Images are all in focus, drone was either stationary or moving at <8km/hr for all images, and there is a massive amount of overlap. Images were obtained from around 25m AGL.

Settings -
410 images 33:01:29

Cannot process dataset

|Options:|auto-boundary: true, dem-resolution: 1, dsm: true, dtm: true, feature-quality: ultra, gps-accuracy: 5, mesh-octree-depth: 13, mesh-size: 500000, min-num-features: 16000, orthophoto-resolution: 0.5, pc-quality: high, resize-to: -1, use-3dmesh: true|

End of the console log-

[INFO] Finished odm_filterpoints stage
[INFO] Running odm_meshing stage
[INFO] Writing ODM Mesh file in: D:\WebODM\resources\app\apps\NodeODM\data\a21f6596-13b2-43af-9bf1-6a072dcd7664\odm_meshing\odm_mesh.ply
[INFO] running “D:\WebODM\resources\app\apps\ODM\SuperBuild\install\bin\PoissonRecon” --in “D:\WebODM\resources\app\apps\NodeODM\data\a21f6596-13b2-43af-9bf1-6a072dcd7664\odm_filterpoints\point_cloud.ply” --out “D:\WebODM\resources\app\apps\NodeODM\data\a21f6596-13b2-43af-9bf1-6a072dcd7664\odm_meshing\odm_mesh.dirty.ply” --depth 13 --pointWeight 4.0 --samplesPerNode 1.0 --threads 15 --bType 2 --linearFit
[WARNING] D:\a\ODM\ODM\SuperBuild\src\PoissonRecon\Src\FEMTree.IsoSurface.specialized.inl (Line 1896)
IsoSurfaceExtractor<3,float,struct VectorTypeUnion<float,struct Point<float,3>,struct Point > >::Extract
bad average roots: 7
[INFO] running “D:\WebODM\resources\app\apps\ODM\SuperBuild\install\bin\OpenMVS\ReconstructMesh” -i “D:\WebODM\resources\app\apps\NodeODM\data\a21f6596-13b2-43af-9bf1-6a072dcd7664\odm_meshing\odm_mesh.dirty.ply” -o “D:\WebODM\resources\app\apps\NodeODM\data\a21f6596-13b2-43af-9bf1-6a072dcd7664\odm_meshing\odm_mesh.ply” --remove-spikes 0 --remove-spurious 20 --smooth 0 --target-face-num 1000000 -v 0
[INFO] Finished odm_meshing stage
[INFO] Running mvs_texturing stage
[INFO] Writing MVS Textured file in: D:\WebODM\resources\app\apps\NodeODM\data\a21f6596-13b2-43af-9bf1-6a072dcd7664\odm_texturing\odm_textured_model_geo.obj
[INFO] running “D:\WebODM\resources\app\apps\ODM\SuperBuild\install\bin\texrecon” “D:\WebODM\resources\app\apps\NodeODM\data\a21f6596-13b2-43af-9bf1-6a072dcd7664\opensfm\undistorted/reconstruction.nvm” “D:\WebODM\resources\app\apps\NodeODM\data\a21f6596-13b2-43af-9bf1-6a072dcd7664\odm_meshing\odm_mesh.ply” “D:\WebODM\resources\app\apps\NodeODM\data\a21f6596-13b2-43af-9bf1-6a072dcd7664\odm_texturing\odm_textured_model_geo” -d gmi -o gauss_clamping -t none --no_intermediate_results --max_texture_size=8192
D:\WebODM\resources\app\apps\ODM\SuperBuild\install\bin\texrecon (built on Jul 29 2022, 19:52:13)
Load and prepare mesh:
Reading PLY: 468863 verts… 939591 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 “D:\WebODM\resources\app\apps\ODM\stages\odm_app.py”, line 88, in execute
self.first_stage.run()
File “D:\WebODM\resources\app\apps\ODM\opendm\types.py”, line 371, in run
self.next_stage.run(outputs)
File “D:\WebODM\resources\app\apps\ODM\opendm\types.py”, line 371, in run
self.next_stage.run(outputs)
File “D:\WebODM\resources\app\apps\ODM\opendm\types.py”, line 371, in run
self.next_stage.run(outputs)
[Previous line repeated 4 more times]
File “D:\WebODM\resources\app\apps\ODM\opendm\types.py”, line 352, in run
self.process(self.args, outputs)
File “D:\WebODM\resources\app\apps\ODM\stages\mvstex.py”, line 117, in process
system.run(’"{bin}" “{nvm_file}” “{model}” “{out_dir}” ’
File “D:\WebODM\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.

All I could salvage from the task was a screen grab of odm_mesh.ply, which was rather disappointing!

Suggestions on how to avoid this error are most welcome

I’ll have a go at another set I took, covering a larger area from ~50-60m AGL

Same problem here-

Too many "No proper input scene descriptor given" failed tasks

I really need to get to the bottom of these no proper input descriptor given failures, which happen too often, and after many (wasted) hours of processing. This morning’s failure after over 41 hours with 590 images was a subset of a 2323 image dataset that completed successfully after 85 hours. I ran the full set with high/medium feature/PC quality settings, and was attempting ultra/ultra with the subset of ~1/4 of the images. 590 images 41:21:11 Cannot process dataset |Options:|auto-bound…

[smathermather]

Link to the images? I’ll try them on my infrastructure.

[Gordon]

Thanks Stephen, I’m uploading now, and will post a link when finished, which should be in about 5 hours over my slow internet.

[smathermather]

Ran with defaults dsm/dtm fine. Rerunning now with just feature-quality turned up.

[Gordon]

‘Feature_quality: ultra’ seems to be a common factor (100%) with this error, and although not every task using ultra feature quality fails, every one that did fail with ultra completed successfully when feature quality was set to high.

EDIT - UPDATE: as suspected, running high feature quality has allowed it to complete without error.

I’ll post results in The Showroom Landslip thread