Hi, there!
I’m trying to process a big project with 4890 images (still more to come. I estimate +1000 images to complete this job) with ODM Native running on a Droplet (Digital Ocean) with 192GB RAM and 32 vCPUs + 1.8TB volume, Ubuntu 16.04.
The last issue I’ve stumble on when ODM starts to process “OpenSfM transformation matrix”, with the following ouput:
[INFO] Running ODM Texturing Cell - Finished
[INFO] Running ODM Georeferencing Cell
[INFO] Running georeferencing with OpenSfM transformation matrix
[DEBUG] running /code/build/bin/odm_georef -bundleFile /home/webodm/proj_fazendaOmega/opensfm/bundle_r000.out -inputTransformFile /home/webodm/proj_fazendaOmega/opensfm/geocoords_transformation.txt -inputCoordFile /home/webodm/proj_fazendaOmega/odm_georeferencing/coords.txt -inputFile /home/webodm/proj_fazendaOmega/odm_texturing/odm_textured_model.obj -outputFile /home/webodm/proj_fazendaOmega/odm_texturing/odm_textured_model_geo.obj -inputPointCloudFile /home/webodm/proj_fazendaOmega/smvs/smvs_dense_point_cloud.ply -outputPointCloudFile /home/webodm/proj_fazendaOmega/odm_georeferencing/odm_georeferenced_model.ply -logFile /home/webodm/proj_fazendaOmega/odm_georeferencing/odm_georeferencing_log.txt -outputTransformFile /home/webodm/proj_fazendaOmega/odm_georeferencing/odm_georeferencing_transform.txt -georefFileOutputPath /home/webodm/proj_fazendaOmega/odm_georeferencing/odm_georeferencing_model_geo.txt
Segmentation fault (core dumped)
Traceback (most recent call last):
File “/code/run.py”, line 47, in
plasm.execute(niter=1)
File “/code/scripts/odm_georeferencing.py”, line 127, in process
‘-logFile {log} -outputTransformFile {transform_file} -georefFileOutputPath {geo_sys}’.format(**kwargs))
File “/code/opendm/system.py”, line 34, in run
raise Exception(“Child returned {}”.format(retcode))
Exception: Child returned 139
Here is the command I used, with the only option to start-with odm_georeferencing, since the first part took almost 48 hours to run…:
python /code/run.py proj_fazendaOmega --start-with odm_georeferencing 2>&1 | tee ./proj_fazendaOmega/log-24out2018.txt
The process just begins to write on files odm_georeferencing_transform.txt, odm_geocoords_transformation.txt (just 4 lines) and quits with the message above. The Droplet have lots of disk space.
The process apparently is able to complete writing the file coords.txt, with 4892 lines (4890 ref to the images + 2 headlines, I think) then stops when begining to write those two txt files.
Strangely, the last values are zeroes:
odm_georeferencing_transform.txt:
|[ 1.0004297,|0.0114977,|0.0000000,|769106.5625155 ]|
|[ -0.0114977,|1.0004297,|0.0000000,|-1685242.3864058 ]|
|[ 0.0000001,|0.0000001,|1.0000000,|-0.0000000 ]|
|[ 0.0000000,|0.0000000,|0.0000000,|1.0000000 ]|
odm_geocoords_transformation.txt:
1.0004296840634197 0.011497707571834326 0.0 769106.5625155289
-0.01149771036580205 1.0004296808037907 2.3283064365386963e-10 -1685242.3864057753
7.82310962677002e-08 8.009374141693115e-08 1.0 -1.862645149230957e-09
0.0 0.0 0.0 1.0
The coords.txt file, on the other side, has no zero values.
I’m not sure those figures means something, but I’m running crazy trying to find what is going on…
Does anyone know what is the meaning of the “139” error or what to do on this situation?
Any help is more than welcome!
Thanks a lot!