Code 1 exception

brantel · 7 April 2018 22:34

I have been trying to get this dataset to run:

I can’t seem to find a combination of options to get it to run. I keep getting Process Exited with Code 1.

I have ran other datasets so I know my install must be OK.

What in the world do I have to do to get this to run? I am very much a newbie and have little knowledge of what all these options do…trying to get a decent 3D model out of it. I have been able to get a decent 3D model using DD and Autodesk recap photo using the same dataset.

I am running Docker for Windows. Lastest versions of everything from the Maser branch. 8cpus, 5888mb memory (host as 8gb), 4096mb swap.

Please let me know what else you might need to know to help me!

Thanks!

pierotofy · 7 April 2018 22:48

Could you copy/paste the output of the task’s console? Code 1 is a very generic error and could mean a lot of things.

brantel · 7 April 2018 23:55

(post withdrawn by author, will be automatically deleted in 24 hours unless flagged)

brantel · 8 April 2018 00:14

Absolutely! Have no idea why but my prior post got flagged???

Here are the results with 139 images, nadir, high obliques, medium obliqes as well as low level obliques.
Default settings with the exception of Force CCD:7.81 (DJI Mavic Air)
Complete Recordset

Here are the results with 110 images, nadir, high obliques as well as medium obliques.
Default settings with the exception of Force CCD:7.81 (DJI Mavic Air)
Less Low Level Obliques

brantel · 8 April 2018 00:16

Here are the results with 71 images, nadir and high obliques.
Default settings with the exception of Force CCD:7.81 (DJI Mavic Air)
Less low and mid level obliques

Here are the results with 3 images, nadir only.
Default settings with the exception of Force CCD:7.81 (DJI Mavic Air)
Nadir only

Thanks for the help!

brantel · 8 April 2018 00:43

I am trying to reply but all my post are being hidden?

I have no idea why or what to do to fix the situation.

pierotofy · 8 April 2018 02:44

Based on your data I would try to set both --matcher-neighbors and --matcher-distance to 0. See https://github.com/OpenDroneMap/OpenDroneMap/wiki/Run-Time-Parameters

If that doesn’t work, I would also try to increase min-num-features to 10000 or 12000.

Posts are being flagged because you are a new users and you are posting a lot of links.

brantel · 8 April 2018 16:08

Tried the first suggestion with setting both --matcher-neighbors and --matcher-distance to 0. It ran for 2:13:55 and then exited with code 1:

Matcher Neighbors turned off

I am now running it with increased min-num-features set to 12000.

brantel · 8 April 2018 22:39

Looks like I am going to have to find a better host with more memory. I am pretty sure my last 2 attempts to run ran out of memory. The first one went over 3:30:00 and the second attempt ran for 3:30:00 and in both cases the “worker” container crashed in the background leading to KILLED being displayed in the log console.

brantel · 10 April 2018 11:28

Doubled the memory in my host to 16Gb and cranked it up in the VM and was able to run the data set.

Here are the results with these settings:

Options: min-num-features: 12000, orthophoto-resolution: 40, matcher-neighbors: 0, force-ccd: 7.81, matcher-distance: 0

full size link

Any ideas to improve the quality more other than take better photos without so many shadows?

Here is an example of the same data set from Autodesk Recap Photo. Notice the Mini is totally missing but the power line is not big and fat.

full size link

Amazing software guys! Keep up the good work!