Dense cloud processing times with add corrections optimization

[Paulo]

In previous version 1.6.1, it was noted that depth maps / dense cloud / model processing times was considerably higher when Camera Optimization was done with Fit Additional corrections option. To check if latest release improved on this discrepancy, i generated a dense cloud on a 71 image 20 Mpix data set.

First with No add corrections optimization and second with add corrections optimization....

The following file shows  the results obtained...

The total time (depth maps + dense cloud) is still about 35 % higher when optimizing with additional corrections....

It would be nice it this could be reduced!

Test was done on Intel(R) Core(TM) i7-3630QM CPU @ 2.40GHz, GeForce GTX 670MX GPU and 16GB RAM.
   

[Alexey Pasumansky]

Hello Paul,

Do you have the processing logs for the both runs?

[Paulo]

Hello Alexey,

attached are logs for both processing runs....

En cases like Phantom 4 RTK camera, it is important to have additional corrections enabled in optimization as results are much better compared to no additional corrections ... see residuals on markers for both optimizations...so reducing processing times using additional corrections  would be great

   Optimize with Additional Corrections                  
Marker   LongErr   LatErr   AltErr   Accura.   TotErr   Proj.       ErrPix
MC07   -0.021    0.039    0.035   0.02           0.057   5          0.382
H56            0.020   -0.013   -0.029   0.02           0.038   6          0.243
H37            0.004   -0.014   -0.017   0.02           0.022   3          0.335
H52    -0.003   -0.012    0.011   0.02         0.016   6          0.132
   Optimize with No Additional Corrections                  
MC07   -0.057    0.084    0.226   0.02    0.248   5          2.162
H56            0.003   -0.035   -0.190   0.02    0.193   6          1.265
H37      0.007   -0.049   -0.108   0.02    0.119   3          2.327
H52     0.047    0.001    0.072   0.02    0.086   6          0.367