[OpenDroneMap-users] How to adjust processing parameters based on quality requirements

[Simon]

Hello Khyale,

first of all OpenDroneMap is not as mature as other mentioned SW
products, thus you will need some work to get into the details of the
program.
>From my point of view, not every parameter is equally "effective" on
every dataset. So at the moment there is some "try and error" involved.

In general: Using --resize-to is the first option you should try. This
will define the image size for the whole workflow. Less pixels are
leading in general to faster processing times (and sparser
reconstructions), more pixels to a better reconstruction (but there is a
chance to run into memory problems as well)...

Try something around 800, 2000, and 3000 for example and examine the
results.

The other parameters are described here:
https://github.com/OpenDroneMap/OpenDroneMap/wiki/3.-Run-Time-Parameters

Keep in mind, that you can rerun the program from a specific step, so
you dont need to do it all over again.
Its also a very good idea to backup your results and name them
accordingly, because ODM overwrites the output constantly.

Cheers!
Simon

On 06/02/2016 08:22 PM, Khyale Nascimento wrote:
>
> Dear colleagues,
>
> First, congratulations for the development of OpenDroneMap project. I
> just install OpenDroneMap in a Linux machine and I need some help to
> choose the parameters to perform a low, normal or high quality
> processing. The images were acquired with inpireOne DJI drone (4K
> camera, gimbal). I have 42 aerial images with  12M pixels  (3992 x
> 2992), jpeg, geoTagged, captured at 60m height, ground sample distance
> (GSD) of 2.5cm / pixel. 
>
> I guess the processing quality parameters are:
>  --resize-to
> --use-opensfm
> --min-num-features
> --matcher-threshold
> --matcher-ratio
> --matcher-neighbors
> --matcher-distance
> --cmvs-maxImages
> --pmvs-level
> --pmvs-csize
> --pmvs-threshold
> --pmvs-wsize
> --pmvs-minImageNum
> --odm_meshing-maxVertexCount
> --odm_meshing-octreeDepth
> --odm_meshing-samplesPerNode
> --odm_meshing-solverDivide
> --odm_texturing-textureResolution
> --odm_texturing-textureWithSize
> --odm_orthophoto-resolution
>
> I do not know the details behind the algoritms, but I want to tune the
> parameters to processing my set of images in low (quick), normal
> (standard) or high (slow) quality results. Can you help me? I know
> theses terms 'low', 'normal', 'high' are very subjective. But I need
> know a way to fine tuning the processing for show the results, compare
> it with other softwares, eg Pix4D, etc.
>
> I am running  in a machine with Linux, Debian 8, amd64, with 12
> processors (Intel Xeon 2.3Ghz), 32GB RAM. It is a HP Z820 workstation.
>
> Thank you,
> Khyale
>
>    
>
>
>
>
>
>
> _______________________________________________
> OpenDroneMap-users mailing list
> OpenDroneMap-users at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/opendronemap-users