Naviglio-italy-processing-failed-4294967295/22437

Hello, i have recently purchsed again WebODM (but the latest upgrade version); i had purchased some years ago the first version, but it worked well and i had never had this kind of problem that doesn’t allow the process to end. Now, i have this issue with processing in WebODM. I need processing a dataset of 115 photos and another dataset of 2100 photos. All photos are georeferenced by onboard RTK gnss with a 3 cm max error in positioning.
Front overlap about 85/95%; side overlap 80%.

Then, i’d like to know if is it possible to allocate more RAM. How can I do it? because my PC does not have 16 GB, but 32 GB. Thank you for your support

You can find the little dataset (115 photos) here: Transfer - Dropbox

Could you help me suggesting me the best setting in order to obtain Ortophoto and DEM (DSM+DTM).
I don’t know which error occurs. I notate that, despite my desktop PC has 32 Gb RAM, WebODM allocation is just of 16 Gb. Could it be the reason for the processing problem? How can I allocate more dedicated RAM to the process in webODM?

"[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.5.4 documentation
100 - done

Activity Output:
Finalizing texture atlases… done. (Took: 0s)
Building objmodel:
Saving model… done.
Whole texturing procedure took: 40.528s
[INFO] Finished mvs_texturing stage
[INFO] Running odm_georeferencing stage
[INFO] Georeferencing point cloud
[INFO] running pdal translate -i “H:\WebODM\resources\app\apps\NodeODM\data\58c7fb8f-13dd-4af7-9eea-3b67ecf956ca\odm_filterpoints\point_cloud.ply” -o “H:\WebODM\resources\app\apps\NodeODM\data\58c7fb8f-13dd-4af7-9eea-3b67ecf956ca\odm_georeferencing\odm_georeferenced_model.laz” ferry transformation --filters.ferry.dimensions=“views => UserData” --filters.transformation.matrix=“1 0 0 493605.0 0 1 0 5029734.0 0 0 1 0 0 0 0 1” --writers.las.offset_x=493605.0 --writers.las.offset_y=5029734.0 --writers.las.scale_x=0.001 --writers.las.scale_y=0.001 --writers.las.scale_z=0.001 --writers.las.offset_z=0 --writers.las.a_srs=“+proj=utm +zone=32 +datum=WGS84 +units=m +no_defs +type=crs”
[INFO] Calculating cropping area and generating bounds shapefile from point cloud
[INFO] running pdal translate -i “H:\WebODM\resources\app\apps\NodeODM\data\58c7fb8f-13dd-4af7-9eea-3b67ecf956ca\odm_georeferencing\odm_georeferenced_model.laz” -o “H:\WebODM\resources\app\apps\NodeODM\data\58c7fb8f-13dd-4af7-9eea-3b67ecf956ca\odm_georeferencing\odm_georeferenced_model.decimated.las” decimation --filters.decimation.step=40
[INFO] running pdal info --boundary --filters.hexbin.edge_size=1 --filters.hexbin.threshold=0 “H:\WebODM\resources\app\apps\NodeODM\data\58c7fb8f-13dd-4af7-9eea-3b67ecf956ca\odm_georeferencing\odm_georeferenced_model.decimated.las” > “H:\WebODM\resources\app\apps\NodeODM\data\58c7fb8f-13dd-4af7-9eea-3b67ecf956ca\odm_georeferencing\odm_georeferenced_model.boundary.json”
[INFO] running pdal info --summary “H:\WebODM\resources\app\apps\NodeODM\data\58c7fb8f-13dd-4af7-9eea-3b67ecf956ca\odm_georeferencing\odm_georeferenced_model.laz” > “H:\WebODM\resources\app\apps\NodeODM\data\58c7fb8f-13dd-4af7-9eea-3b67ecf956ca\odm_georeferencing\odm_georeferenced_model.summary.json”
[INFO] running ogr2ogr -overwrite -f GPKG -a_srs “+proj=utm +zone=32 +datum=WGS84 +units=m +no_defs” “H:\WebODM\resources\app\apps\NodeODM\data\58c7fb8f-13dd-4af7-9eea-3b67ecf956ca\odm_georeferencing\odm_georeferenced_model.bounds.gpkg” “H:\WebODM\resources\app\apps\NodeODM\data\58c7fb8f-13dd-4af7-9eea-3b67ecf956ca\odm_georeferencing\odm_georeferenced_model.bounds.geojson”
[INFO] Classifying H:\WebODM\resources\app\apps\NodeODM\data\58c7fb8f-13dd-4af7-9eea-3b67ecf956ca\odm_georeferencing\odm_georeferenced_model.laz using Simple Morphological Filter (1/2)
[INFO] running pdal translate -i H:\WebODM\resources\app\apps\NodeODM\data\58c7fb8f-13dd-4af7-9eea-3b67ecf956ca\odm_georeferencing\odm_georeferenced_model.laz -o H:\WebODM\resources\app\apps\NodeODM\data\58c7fb8f-13dd-4af7-9eea-3b67ecf956ca\odm_georeferencing\odm_georeferenced_model.laz smrf --filters.smrf.scalar=1.25 --filters.smrf.slope=0.15 --filters.smrf.threshold=0.5 --filters.smrf.window=18.0
[INFO] Created H:\WebODM\resources\app\apps\NodeODM\data\58c7fb8f-13dd-4af7-9eea-3b67ecf956ca\odm_georeferencing\odm_georeferenced_model.laz in 0:00:34.056821
[INFO] Classifying H:\WebODM\resources\app\apps\NodeODM\data\58c7fb8f-13dd-4af7-9eea-3b67ecf956ca\odm_georeferencing\odm_georeferenced_model.laz using OpenPointClass (2/2)
[INFO] running pcclassify “H:\WebODM\resources\app\apps\NodeODM\data\58c7fb8f-13dd-4af7-9eea-3b67ecf956ca\odm_georeferencing\odm_georeferenced_model.laz” “H:\WebODM\resources\app\apps\NodeODM\data\58c7fb8f-13dd-4af7-9eea-3b67ecf956ca\odm_georeferencing\odm_georeferenced_model.classified.laz” “C:\ProgramData\ODM\storage\models\openpointclass\v1_0_0\model.bin” -u -s 2,64
Model: Gradient Boosted Trees
Loading C:\ProgramData\ODM\storage\models\openpointclass\v1_0_0\model.bin
Reading points from H:\WebODM\resources\app\apps\NodeODM\data\58c7fb8f-13dd-4af7-9eea-3b67ecf956ca\odm_georeferencing\odm_georeferenced_model.laz
Number of points: 14121050
Label dimension: Classification
Starting resolution: 0.2
Init scale 0 at 0.2 …
Init scale 1 at 0.2 …
Init scale 6 at 6.4 …
Init scale 5 at 3.2 …
Init scale 3 at 0.8 …
Init scale 4 at 1.6 …
Init scale 2 at 0.4 …
Building scale 1 (469864 points) …
Building scale 2 (172020 points) …
Building scale 3 (57636 points) …
Building scale 4 (15941 points) …
Building scale 5 (4006 points) …
Building scale 6 (942 points) …
Features: 126
Classifying…
Local smoothing…
Wrote H:\WebODM\resources\app\apps\NodeODM\data\58c7fb8f-13dd-4af7-9eea-3b67ecf956ca\odm_georeferencing\odm_georeferenced_model.classified.laz
[INFO] Rectifying H:\WebODM\resources\app\apps\NodeODM\data\58c7fb8f-13dd-4af7-9eea-3b67ecf956ca\odm_georeferencing\odm_georeferenced_model.laz using with [reclassify threshold: 5, min area: 750, min points: 500]
[WARNING] Error rectifying ground in file H:\WebODM\resources\app\apps\NodeODM\data\58c7fb8f-13dd-4af7-9eea-3b67ecf956ca\odm_georeferencing\odm_georeferenced_model.laz: Invalid \escape: line 1 column 38 (char 37)
[INFO] Creating Entwine Point Tile output
[INFO] running entwine build --threads 12 --tmp “H:\WebODM\resources\app\apps\NodeODM\data\58c7fb8f-13dd-4af7-9eea-3b67ecf956ca\entwine_pointcloud-tmp” -i “H:\WebODM\resources\app\apps\NodeODM\data\58c7fb8f-13dd-4af7-9eea-3b67ecf956ca\odm_georeferencing\odm_georeferenced_model.laz” -o “H:\WebODM\resources\app\apps\NodeODM\data\58c7fb8f-13dd-4af7-9eea-3b67ecf956ca\entwine_pointcloud”
1/1: H:\WebODM\resources\app\apps\NodeODM\data\58c7fb8f-13dd-4af7-9eea-3b67ecf956ca\odm_georeferencing\odm_georeferenced_model.laz
Dimensions: [
X:int32, Y:int32, Z:int32, Intensity:uint16, ReturnNumber:uint8,
NumberOfReturns:uint8, ScanDirectionFlag:uint8, EdgeOfFlightLine:uint8,
Classification:uint8, ScanAngleRank:float32, UserData:uint8,
PointSourceId:uint16, GpsTime:float64, Red:uint16, Green:uint16, Blue:uint16
]
Points: 14,121,050
Bounds: [(493491, 5029636, 160), (493718, 5029834, 188)]
Scale: 0.01
SRS: EPSG:32632

Adding 0 - H:\WebODM\resources\app\apps\NodeODM\data\58c7fb8f-13dd-4af7-9eea-3b67ecf956ca\odm_georeferencing\odm_georeferenced_model.laz
Joining
00:10 - 36% - 5,058,560 - 1,821 (1,821) M/h - 0W - 0R - 134A
00:20 - 72% - 10,108,928 - 1,819 (1,818) M/h - 0W - 0R - 256A
00:30 - 100% - 14,121,050 - 1,694 (1,444) M/h - 63W - 0R - 290A
Done 0
Saving
Wrote 14,121,050 points.
[INFO] Finished odm_georeferencing stage
[INFO] Running odm_dem stage
[INFO] Create DSM: True
[INFO] Create DTM: True
[INFO] DEM input file H:\WebODM\resources\app\apps\NodeODM\data\58c7fb8f-13dd-4af7-9eea-3b67ecf956ca\odm_georeferencing\odm_georeferenced_model.laz found: True
[INFO] running renderdem “H:\WebODM\resources\app\apps\NodeODM\data\58c7fb8f-13dd-4af7-9eea-3b67ecf956ca\odm_georeferencing\odm_georeferenced_model.laz” --outdir “H:\WebODM\resources\app\apps\NodeODM\data\58c7fb8f-13dd-4af7-9eea-3b67ecf956ca\odm_dem” --output-type max --radiuses 0.02,0.028284271247461905,0.04000000000000001 --resolution 0.05 --max-tiles 0 --decimation 20 --classification -1 --tile-size 4096 --force
Decimation set to 20
Reading points from H:\WebODM\resources\app\apps\NodeODM\data\58c7fb8f-13dd-4af7-9eea-3b67ecf956ca\odm_georeferencing\odm_georeferenced_model.laz
Number of points: 14121050
Classification dimension: Classification

===== Dumping Info for Geeks (developers need this to fix bugs) =====
Child returned 3221225477
Traceback (most recent call last):
File “H:\WebODM\resources\app\apps\ODM\stages\odm_app.py”, line 82, in execute
self.first_stage.run()
File “H:\WebODM\resources\app\apps\ODM\opendm\types.py”, line 470, in run
self.next_stage.run(outputs)
File “H:\WebODM\resources\app\apps\ODM\opendm\types.py”, line 470, in run
self.next_stage.run(outputs)
File “H:\WebODM\resources\app\apps\ODM\opendm\types.py”, line 470, in run
self.next_stage.run(outputs)
[Previous line repeated 6 more times]
File “H:\WebODM\resources\app\apps\ODM\opendm\types.py”, line 449, in run
self.process(self.args, outputs)
File “H:\WebODM\resources\app\apps\ODM\stages\odm_dem.py”, line 66, in process
commands.create_dem(
File “H:\WebODM\resources\app\apps\ODM\opendm\dem\commands.py”, line 82, in create_dem
system.run('renderdem “{input}” ’
File “H:\WebODM\resources\app\apps\ODM\opendm\system.py”, line 112, in run
raise SubprocessException(“Child returned {}”.format(retcode), retcode)
opendm.system.SubprocessException: Child returned 3221225477

===== 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.5.4 documentation
100 - done.

1 Like

Hi,

I think for your project with 115 images 16GB RAM should work. I will have a look at this set.

For your image project of 2100 images you definately need more (physical) RAM. My guess is, depending on the required output resolution somewhere between 64GB and 128GB RAM.

You could also try the (commercial) cloud based option WebODM Lightning: Pricing if you want to process these images in te cloud.

115 images project

Project processed with preset High Resolution, gives nice results. Processed on a 32GB RAM system (Ubuntu).

2 cm/pixel resolution

3d pointcloud

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