Very messy task output of a road

Hmmm, second dataset failed with a “Cannot process dataset”.

Settings were:
auto-boundary: true, dem-resolution: 1, dsm: true, dtm: true, gps-accuracy: 5, mesh-octree-depth: 13, mesh-size: 500000, min-num-features: 15000, orthophoto-resolution: 0.5, pc-filter: 5, pc-quality: ultra, pc-rectify: true, resize-to: -1, use-3dmesh: true

Tail end of log:
[INFO] Running openmvs stage
[INFO] running “/code/SuperBuild/install/bin/opensfm/bin/opensfm” export_openmvs “/var/www/data/22d04bf0-bae8-4622-a37e-e7cd71f12c49/opensfm”
[INFO] Depthmap resolution set to: 2736px
[INFO] Running dense reconstruction. This might take a while.
[INFO] Estimating depthmaps
[INFO] nvidia-smi detected
[INFO] running “/code/SuperBuild/install/bin/OpenMVS/DensifyPointCloud” “/var/www/data/22d04bf0-bae8-4622-a37e-e7cd71f12c49/opensfm/undistorted/openmvs/scene.mvs” --resolution-level 0 --dense-config-file “/var/www/data/22d04bf0-bae8-4622-a37e-e7cd71f12c49/opensfm/undistorted/openmvs/Densify.ini” --min-resolution 2736 --max-resolution 2992 --max-threads 20 --number-views-fuse 2 --sub-resolution-levels 2 -w “/var/www/data/22d04bf0-bae8-4622-a37e-e7cd71f12c49/opensfm/undistorted/openmvs/depthmaps” -v 0 --geometric-iters 0
06:02:00 [App ] Build date: Jul 24 2022, 23:25:19
06:02:00 [App ] CPU: Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz (40 cores)
06:02:00 [App ] RAM: 503.85GB Physical Memory 1.50TB Virtual Memory
06:02:00 [App ] OS: Linux 5.15.0-50-generic (x86_64)
06:02:00 [App ] Disk: 1.52TB (1.79TB) space
06:02:00 [App ] SSE & AVX compatible CPU & OS detected
06:02:00 [App ] Command line: DensifyPointCloud /var/www/data/22d04bf0-bae8-4622-a37e-e7cd71f12c49/opensfm/undistorted/openmvs/scene.mvs --resolution-level 0 --dense-config-file /var/www/data/22d04bf0-bae8-4622-a37e-e7cd71f12c49/opensfm/undistorted/openmvs/Densify.ini --min-resolution 2736 --max-resolution 2992 --max-threads 20 --number-views-fuse 2 --sub-resolution-levels 2 -w /var/www/data/22d04bf0-bae8-4622-a37e-e7cd71f12c49/opensfm/undistorted/openmvs/depthmaps -v 0 --geometric-iters 0
06:02:00 [App ] Find a camera not pointing towards the scene center; the scene will be considered unbounded (no ROI)
06:02:01 [App ] Preparing images for dense reconstruction completed: 143 images (703ms)
06:02:01 [App ] Selecting images for dense reconstruction completed: 0 images (40ms)

Fused depth-maps 0 (100%, 0ms)
06:02:01 [App ] Densifying point-cloud completed: 0 points (752ms)
06:02:01 [App ] MEMORYINFO: {
06:02:01 [App ] VmPeak: 553614616 kB
06:02:01 [App ] VmSize: 553348568 kB
06:02:01 [App ] } ENDINFO
[INFO] running “/code/SuperBuild/install/bin/OpenMVS/DensifyPointCloud” --filter-point-cloud -1 -i “/var/www/data/22d04bf0-bae8-4622-a37e-e7cd71f12c49/opensfm/undistorted/openmvs/scene_dense.mvs” -v 0 --geometric-iters 0
06:02:01 [App ] Build date: Jul 24 2022, 23:25:19
06:02:01 [App ] CPU: Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz (40 cores)
06:02:01 [App ] RAM: 503.85GB Physical Memory 1.50TB Virtual Memory
06:02:01 [App ] OS: Linux 5.15.0-50-generic (x86_64)
06:02:01 [App ] Disk: 1.52TB (1.79TB) space
06:02:01 [App ] SSE & AVX compatible CPU & OS detected
06:02:01 [App ] Command line: DensifyPointCloud --filter-point-cloud -1 -i /var/www/data/22d04bf0-bae8-4622-a37e-e7cd71f12c49/opensfm/undistorted/openmvs/scene_dense.mvs -v 0 --geometric-iters 0
06:02:02 [App ] error: no valid point-cloud for the ROI estimation

===== Dumping Info for Geeks (developers need this to fix bugs) =====
Child returned 1
Traceback (most recent call last):
File “/code/stages/odm_app.py”, line 94, in execute
self.first_stage.run()
File “/code/opendm/types.py”, line 347, in run
self.next_stage.run(outputs)
File “/code/opendm/types.py”, line 347, in run
self.next_stage.run(outputs)
File “/code/opendm/types.py”, line 347, in run
self.next_stage.run(outputs)
[Previous line repeated 1 more time]
File “/code/opendm/types.py”, line 328, in run
self.process(self.args, outputs)
File “/code/stages/openmvs.py”, line 206, in process
system.run(‘“%s” %s’ % (context.omvs_densify_path, ’ '.join(config + gpu_config + extra_config)))
File “/code/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 3.1.7 documentation

I’m trying it again now with these settings:
auto-boundary: true, debug: true, dsm: true, dtm: true, feature-quality: ultra, max-concurrency: 20, verbose: true, rerun-from: dataset