Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - AndyC

Pages: [1] 2
General / Re: flying altitude estimation in processing report
« on: May 10, 2020, 11:04:03 PM »
Hi Alexey,

Is flying height calculated from the median average distance? (Or another average?)


General / Clarify confidence intervals of accuracy terms?
« on: January 15, 2020, 02:06:19 PM »
Could anyone from Agisoft clarify the intended confidence intervals of the 'accuracy' terms for camera and marker geolocations?

(some users seem to assume that these are 1 sigma (68% confidence interval), while others consider them to be 2 sigma (95% confidence interval)).

Not yet, I will do, thanks

Hi Alexey,

Is this implemented yet? (If so, would you be able to share some code?)


Ah, thanks for the update Alexey.

It would be useful once added.

Python and Java API / How to add 'description' string to orthomosaic export?
« on: September 04, 2018, 03:15:21 PM »
We would like to add a string text to the 'description' field in the tiff metadata when exporting orthomosaic tiffs, (in order to facilitate data management).

Adding strings to the description field is available when exporting orthomosaics via Batch Process in the GUI, but we have not been able to implement this in our Python scripts, and this is not described in the API.

Can anyone offer examples of the arguments to include descriptions in orthomosaic exports?

Any suggestions much appreciated,

General / Re: Your opinion on USGS Agisoft Processing Workflow
« on: August 25, 2018, 05:14:09 PM »
Well said Tom, thanks.

General / Re: Slow dense cloud generation with Tesla K80 GPUs
« on: August 20, 2018, 12:45:07 PM »
Ah, we had misunderstood that, thanks for the clarification! (there's a lot of misinformation/ confusion about this step elsewhere online)

Now that I know what to look for, there is more relevant information/confirmation at:


Feature Requests / Differently scaled exports from raster calculator
« on: August 17, 2018, 12:46:24 PM »
We would like to be able to export the outputs of the raster calculator with the direct values, rather than rescaled values.

For example, when using the raster calculator we generate NDVI maps with attribute values ranging from +1 to -0. However, when we export these reflectance maps (e.g. as tif files), the attribute values are rescaled to 0-255. We then have to load these maps into another software to rescale them back to -1 to +1. It would be nice to be able to export the files we need directly from PhotoScan.

Andy & Dave

General / Slow dense cloud generation with Tesla K80 GPUs
« on: August 17, 2018, 12:35:56 PM »
We are encountering unexpectedly slow dense cloud generation on a high-performance cluster. Any help working out the solution would be greatly appreciated!

We have two computer systems:

Workstation: (OS Windows 64; CPU i7-7800X 6-core 3.5 GHz; GPU 1 x  NVIDIA GeForce GTX1080; RAM 128GB DDR4 2133 MHz; Photoscan-Pro 1.4.2 build 6205)

Cluster: (OS Linex; CPU 2x Intel Haswell E5-2640v3 16-core 2.6GHz; GPU 4x NVIDIA Tesla K80; RAM 256 GB DDR4; Photoscan-Pro/1.4.3)

Our test job consists of 489 x 20 MP photos, processed through the initial steps (alignment, precise markers, tie point filtering, optimisation, etc.). All available GPUs are enabled on both systems (x1 on the workstation, x4 on the cluster; either via the GUI or with " = 2 ** len( - 1  # activate all available GPUs"). We will be using Python scripts for (mostly) headless processing. Dense Cloud Generation was attempted at ultrahigh quality with mild depth filtering on both systems.

On the workstation, depth map generation takes 9 hours and dense cloud generation takes 28 hours (37 hours total).
On the cluster, depth map generation takes 5 hours and dense cloud generation takes >28 hours (not complete after 33 hours).

(We thought that there might be unexpected overheads with using the 4 GPUs on the cluster, but our tests with 10 and 100 image sets show processing time consistently decreases (slightly) as the number of GPUs increases).

(1) Would anyone comment on our expectation that this Cluster should complete dense cloud processing substantially (e.g. more than 40%) faster than this Workstation?

(2) Could there be an issue with the GPU not being configured for optimal performance from PhotoScan?
(e.g. the compute mode, as hinted at by Alexey here

We have no experience configuring GPUs, but suggestions are welcome, especially if it might be possible to better optimise the K80s via the Python script.

General / Re: Fly-through of model?
« on: January 25, 2017, 08:44:13 PM »
Cloud compare is pretty powerful and freely available ( - you can use it to make animations and fly throughs which are nice

General / Re: Recommended viewer software
« on: January 25, 2017, 08:37:01 PM »
Another option for interactive: the Cloud compare viewer - nice and lightweight (

Bug Reports / (Minor) Issue with Exporting Point Clouds
« on: March 13, 2016, 02:08:57 PM »
I've noticed a minor interface issue when exporting point clouds from PS v1.2.3_2331. In the Export Points tool, when selecting source data, the drop down options are 'sparse' or 'dense' clouds; however, once selected, these descriptors are replaced with either 'yes' or 'no', which are somewhat ambiguous. It would be useful to change this to display 'sparse' or 'dense' once selected.

Only a very minor issue, but hopefully it will help continue making PS even more accessible to new users.
Cheers, Andy

Bug Reports / Re: Build Mesh stopped working in PhotoScan 1.2.3
« on: March 12, 2016, 10:38:43 PM »
I'm encountering the same problems with Build Mesh freezing at ca. 90% on the 'Calculating vertex colours...' step.

Configuration: PS v 1.2.3_2331; Build Mesh settings: height field, face count=low(10,000), source=sparse cloud. I've had the same error three times, including leaving the system for 20 hours with no progress (this should not be memory limitations, as this is a small job on a very high spec system that has previously handled much larger jobs). There is also no response when I attempt to terminate the process (the time elapsed counter simple continues for several more hours).

General / Re: Understanding Image Residuals
« on: February 09, 2016, 06:36:23 PM »
Thanks Alexey,

I think I was a little confused because this is output was directly below the title 'Camera Calibration' and above the parameters of the lens calibration model in the processing report .
I can't seem to access the distortion plot you described from within the camera calibration window - Is this something new to the latest version (I've still using Version 1.1.5 build 2034)?


Pages: [1] 2