Attempting to do a detailed 3D model of a power pole (which has lots of features due to it falling apart!) I encountered this PoissonRecon failure.
Any suggestions as to what might cause that?
323 images 60:14:11
Cannot process dataset
|Options:|auto-boundary: true, boundary: {“type”:“FeatureCollection”,“features”:[{“type”:“Feature”,“properties”:{},“geometry”:{“type”:“Polygon”,“coordinates”:[[[151.05253279209137,-31.331298169293767]…,]}, dem-resolution: 1, dsm: true, dtm: true, feature-quality: ultra, gps-accuracy: 6, mesh-octree-depth: 13, mesh-size: 350000, orthophoto-resolution: 0.3, pc-filter: 5, pc-geometric: true, pc-quality: ultra, resize-to: -1, use-3dmesh: true|
End of the console log -
?> Parameters:
input = E:\WebODM\resources\app\apps\NodeODM\data\981e80b5-02b5-4c9c-ba9b-384caef99f1d\opensfm\undistorted\openmvs\scene_dense_dense_filtered.ply
output = E:\WebODM\resources\app\apps\NodeODM\data\981e80b5-02b5-4c9c-ba9b-384caef99f1d\odm_filterpoints\point_cloud.ply
std = 5
meanK = 16
boundary = 17 polygon vertexes
concurrency = 16
verbose = no
→ Setting num_threads to 16
→ Cropping
→ Done cropping in 104.8s
?> Skipping sampling
→ Statistical filtering
?> Done in 288s
→ Writing output
?> Done in 170.4s
?> Pipeline done in 563.2s
[INFO] Finished odm_filterpoints stage
[INFO] Running odm_meshing stage
[INFO] Writing ODM Mesh file in: E:\WebODM\resources\app\apps\NodeODM\data\981e80b5-02b5-4c9c-ba9b-384caef99f1d\odm_meshing\odm_mesh.ply
[INFO] running “E:\WebODM\resources\app\apps\ODM\SuperBuild\install\bin\PoissonRecon” --in “E:\WebODM\resources\app\apps\NodeODM\data\981e80b5-02b5-4c9c-ba9b-384caef99f1d\odm_filterpoints\point_cloud.ply” --out “E:\WebODM\resources\app\apps\NodeODM\data\981e80b5-02b5-4c9c-ba9b-384caef99f1d\odm_meshing\odm_mesh.dirty.ply” --depth 13 --pointWeight 4.0 --samplesPerNode 1.0 --threads 15 --bType 2 --linearFit
[WARNING] Child returned 3221226505
[WARNING] PoissonRecon failed with 7 threads, let’s retry with 3…
[INFO] running “E:\WebODM\resources\app\apps\ODM\SuperBuild\install\bin\PoissonRecon” --in “E:\WebODM\resources\app\apps\NodeODM\data\981e80b5-02b5-4c9c-ba9b-384caef99f1d\odm_filterpoints\point_cloud.ply” --out “E:\WebODM\resources\app\apps\NodeODM\data\981e80b5-02b5-4c9c-ba9b-384caef99f1d\odm_meshing\odm_mesh.dirty.ply” --depth 13 --pointWeight 4.0 --samplesPerNode 1.0 --threads 7 --bType 2 --linearFit
[WARNING] Child returned 3221226505
[WARNING] PoissonRecon failed with 3 threads, let’s retry with 1…
[INFO] running “E:\WebODM\resources\app\apps\ODM\SuperBuild\install\bin\PoissonRecon” --in “E:\WebODM\resources\app\apps\NodeODM\data\981e80b5-02b5-4c9c-ba9b-384caef99f1d\odm_filterpoints\point_cloud.ply” --out “E:\WebODM\resources\app\apps\NodeODM\data\981e80b5-02b5-4c9c-ba9b-384caef99f1d\odm_meshing\odm_mesh.dirty.ply” --depth 13 --pointWeight 4.0 --samplesPerNode 1.0 --threads 3 --bType 2 --linearFit
[WARNING] Child returned 3221226505
[WARNING] PoissonRecon failed with 1 threads, let’s retry with 0…
[INFO] running “E:\WebODM\resources\app\apps\ODM\SuperBuild\install\bin\PoissonRecon” --in “E:\WebODM\resources\app\apps\NodeODM\data\981e80b5-02b5-4c9c-ba9b-384caef99f1d\odm_filterpoints\point_cloud.ply” --out “E:\WebODM\resources\app\apps\NodeODM\data\981e80b5-02b5-4c9c-ba9b-384caef99f1d\odm_meshing\odm_mesh.dirty.ply” --depth 13 --pointWeight 4.0 --samplesPerNode 1.0 --threads 1 --bType 2 --linearFit
[WARNING] Child returned 3221226505
[INFO] running “E:\WebODM\resources\app\apps\ODM\SuperBuild\install\bin\OpenMVS\ReconstructMesh” -i “E:\WebODM\resources\app\apps\NodeODM\data\981e80b5-02b5-4c9c-ba9b-384caef99f1d\odm_meshing\odm_mesh.dirty.ply” -o “E:\WebODM\resources\app\apps\NodeODM\data\981e80b5-02b5-4c9c-ba9b-384caef99f1d\odm_meshing\odm_mesh.ply” --remove-spikes 0 --remove-spurious 20 --smooth 0 --target-face-num 700000 -v 0
===== Dumping Info for Geeks (developers need this to fix bugs) =====
Child returned 1
Traceback (most recent call last):
File “E:\WebODM\resources\app\apps\ODM\stages\odm_app.py”, line 94, in execute
self.first_stage.run()
File “E:\WebODM\resources\app\apps\ODM\opendm\types.py”, line 346, in run
self.next_stage.run(outputs)
File “E:\WebODM\resources\app\apps\ODM\opendm\types.py”, line 346, in run
self.next_stage.run(outputs)
File “E:\WebODM\resources\app\apps\ODM\opendm\types.py”, line 346, in run
self.next_stage.run(outputs)
[Previous line repeated 3 more times]
File “E:\WebODM\resources\app\apps\ODM\opendm\types.py”, line 327, in run
self.process(self.args, outputs)
File “E:\WebODM\resources\app\apps\ODM\stages\odm_meshing.py”, line 24, in process
mesh.screened_poisson_reconstruction(tree.filtered_point_cloud,
File “E:\WebODM\resources\app\apps\ODM\opendm\mesh.py”, line 208, in screened_poisson_reconstruction
system.run(’"{reconstructmesh}" -i “{infile}” ’
File “E:\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. Have you followed best practices for data acquisition? See Flying Tips — OpenDroneMap 2.8.4 documentation