Forum

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 - Toll

Pages: [1] 2
1
General / projection file - AGD66 EPSG20255 + AHD heights
« on: March 26, 2019, 07:13:59 AM »
hi team,

we have some equipment that exports either WGS84 lat/long and ellipsoid heights, or WGS84 lat/long and AHD heights.

we are having alot of trouble coordinating the Z value of the projects due to incorrect height transformation.

is it possible to be supplied with a WGS84 projection file with AHD as the vertical datum?

Using the standard wgs84 to convert the ellipsoid heights isnt accurate due to a local datum being used.

thanks!

2
General / Separate areas in the one chunk - works MOST of the time
« on: February 19, 2019, 03:00:55 AM »
morning Alexey,

we generally process discrete areas from a single RPA flight in the one chunk (with no overlap between areas) and the alignment process works just fine for all cameras (see attachment report mulit-job.jpg)

however lately, with one particular RGB camera, it only aligns one of the areas-rather than all areas. We have tried disabling one section of cameras, which allows the other section to align, but they wont process together. (refer photoscan attachment separate.jpg)

after aligning photos, we have tried resizing the region to encompass all images, however a re-alignment still only aligns the first section and the region is resized to the extents of the first area. I found a forum post from a few years ago, discussing why it SHOULDNT work (mulitple areas without overlap), but this doesn't explain why it DOES work with one of our RGB cameras, but not the other.

i have also tried selecting the unaligned photos and 'aligning selected cameras', but this doesnt do anything.

your help here would be appreciated. we are using photoscan 1.3.4

thanks!

3
Python and Java API / Boundary export option
« on: January 31, 2019, 08:35:41 AM »
hi Alexey

i notice since V1.4.3, an outer boundary is now used to clip the exported models.  Previously this was only applicable to ortho/dem.

whilst i can appreciate the convenience of this feature, is it possible to implement (if it doesn't exist already, as i cant see it in the API) a flag we can set as to whether a particular export should honour the boundary or not?

for now we are re-importing our shape as 'noboundary' and running the exports. it works - but hoping it can be neater?

thanks!

4
General / Re: Thermal orthomosaic - Flir Duo Pro R
« on: September 21, 2018, 11:37:54 PM »
I'm not sure if this information will help you. But we are successfully using agisoft for thermal ortho photo using flir camera for DJI.

We save as tiff ( I think it is radiometric because the photo preview on windows is all black, but when loading into GIS, it is a raster with cell values in~7000).

We use raster calculator in photoscan and apply the conversion to degrees Celsius as per info on flir website. 

This gives all photos in photoscan colour, which we then proceed as normal for Align/cloud/ortho

5
Sorry, as per another thread a restart solved the issue

6
Hi Alexey, I have copied this code to my own script and I receive the error,

Sensor.user_calib = calib
AttributeError: Photoscan.Sensor object attribute 'user_calib' is read-only

Any ideas?

7
Bug Reports / Re: cudastreamdestroy failed error
« on: October 24, 2017, 01:31:14 PM »
Thanks Alexey

I have reinstalled the 387.92 drivers and restarted between each of the following

204, 16mp pictures

Lowest align/Lowest dense cloud cpu+gpu#0  = success

Lowest align/Lowest dense cloud cpu+gpu#1  = error on depth reconstruction, launch timed out and was terminated at line 156

Lowest align/Lowest dense cloud cpu+gpu#2  = success

Lowest align/Lowest dense cloud cpu+gpu#1 (again) = success

Lowest align/Lowest dense cloud cpu+gpu#0+gpu#1  = success

Lowest align/Lowest dense cloud cpu+gpu#0+gpu#2  = success

Lowest align/Lowest dense cloud cpu+gpu#1+gpu#2  = success

Lowest align/Lowest dense cloud cpu+gpu#0+gpu#1+gpu#2  = error on depth reconstruction, program crashed, gpu rectifying failed, kernel failed. Launch timeouts on 164,749 and 156.

Lowest align/Lowest dense cloud cpu+gpu#0+gpu#1+gpu#2 (again) = success, but noticeable pauses in the depth reconstruction. Also slowest alignment time... Same depth time as 2gpu.

Lowest align/Lowest dense cloud cpu+gpu#0+gpu#2  = success

Lowest align/Lowest dense cloud cpu+gpu#0  = success

Lowest align/Lowest dense cloud gpu#0+gpu#1+gpu#2  = fastest alignment, no pauses, success

Med align/med dense cloud, gpu0+1+2 = kernel failed: launch timeouts at line 184,749,156

Still testing...

Med align/med dense cloud, gpu0+1 = software crashed, kernel failed: launch timeouts at line 194,191

Med align/med dense cloud, gpu0+2 = success

Med align/med dense cloud, gpu0+1+2= Bsod dpc watchdog violation

Med align/med dense cloud, gpu0+2 = success

med align/med dense cloud, gpu 1+2 = fail, 2017-10-24 21:39:51 GPU rectifying failed: unknown error at line 212Error: Kernel failed: unknown error at line 749, 801,156

med align/med dense cloud, gpu 1+2 = fail, kernel failed, lines 194,307,749

is there something wrong with gpu1?? temps only got to 70degrees..

8
Bug Reports / Re: cudastreamdestroy failed error
« on: October 24, 2017, 12:13:37 PM »
back to 1.3.1 and:

2017-10-24 19:12:16 photo 22: 24922 points
2017-10-24 19:12:17 photo 1: 27382 points
2017-10-24 19:12:17 photo 23: 26058 points
2017-10-24 19:12:17 Warning: unspecified launch failure
2017-10-24 19:12:17 Warning: unspecified launch failure
2017-10-24 19:12:17 Warning: unspecified launch failure
2017-10-24 19:12:17 Finished processing in 7.754 sec (exit code 0)
2017-10-24 19:12:17 Error: Kernel failed: unspecified launch failure at line 222

1.3.1 and NVidia version 387.92 (the screen flashed black just as it crashed)

2017-10-24 19:21:46 photo 11: 16798 points
2017-10-24 19:21:46 photo 12: 16205 points
2017-10-24 19:21:47 photo 13: 17233 points
2017-10-24 19:21:53 photo 2: 24814 points
2017-10-24 19:21:53 photo 1: 26094 points
2017-10-24 19:21:53 Finished processing in 11.088 sec (exit code 0)
2017-10-24 19:21:53 Error: all CUDA-capable devices are busy or unavailable at line 91

as above, settings was low alignment, low densecloud, error when processing densecloud (attached)

9
Bug Reports / Re: cudastreamdestroy failed error
« on: October 24, 2017, 12:10:38 PM »
For some extra info,

I have downgraded to 1.2.6 and when on 'reconstructing depth'

I get ocl_engine.cpp line 231: clenqueuewritebuffer failed, cl_out_of_resources
Gpu processing failed, switching to cpu mode

10
Bug Reports / cudastreamdestroy failed error
« on: October 24, 2017, 11:34:05 AM »
hello

running agisoft 1.3.4  build 5067 on a xeon 2687w v4, 3x1080.

I am getting the attached error as soon as I started 'align photos'

2017-10-24 18:24:39 Warning: cudaStreamDestroy failed: all CUDA-capable devices are busy or unavailable (46)
2017-10-24 18:24:45 Finished processing in 12.54 sec (exit code 0)
2017-10-24 18:24:45 Error: unspecified launch failure (4) at line 119

and a windows 10 notification of "application has been blocked from accessing Graphics hardware"

I have enabled the 3 x gpu's in preferences and disabled the CPU.

disabling GPU's and enabling CPU's allows the align photos to start. It is still processing, so no comments yet on the dense cloud generation.

I have tried multiple versions of agisoft and multiple version of Nvidia driver between 385.28 to 388.0

we have another system with different specs that doesn't have any issues.
can you help please Alexey!?

thanks

11
Python and Java API / Re: 'null' value on exportOrthomosaic
« on: October 04, 2017, 12:59:11 AM »
Hi Alexey,
i see this option is now available in the GUI for exportmosaic in version 1.3.1, but i see no reference of it in the python 1.3 API?

is this available too please?

12
General / System configuration check please
« on: September 07, 2017, 11:00:14 PM »
Time has come for us to invest in a few more processing nodes.  I'm still tied up as to whether to go for high GHz i9 or stick with dual 2687v4.  We intend to equip with 4x1080. As you can tell Pryce isn't really an issue, but any decrease in processing time is key.

Would really appreciate some suggestions on cpu, as I have read so much here now I don't know which way to go!

Dual 2687v3 ( or i9 7900x , i7 7820x, i7 7740x,)
128gb ram
4x1080

I am concerned that not having enough CPU cores will affect when we enable 4xgpu.

We process with a custom script with the below job settings

Photos: 200-1000
Res,: 20mp
Alignment: high
Dense cloud: medium

Any help you could give would be great please

13
Python and Java API / 'null' value on exportOrthomosaic
« on: March 07, 2017, 09:13:05 AM »
good afternoon,

i thought i remember seeing somewhere that the null or background value for an exported Orthomosaic changed in the latest 1.3.0

previous release 1.2.3 had a background value of 0,0,0, but version 1.3.0 has background value 255,255,255

is this easily changed somewhere? i cant see it as an option in the API.

we would like to change it because we have alot of downstream processes setup to use 0,0,0

thanks

14
General / Re: Customising Open_CL max group size settings
« on: March 07, 2017, 09:09:02 AM »
is this a valid concern? i see no other way of maximising the GPU usage with the resampled picture size

15
Python and Java API / Re: Bug? chunk.exportModel & vertex colors
« on: March 26, 2016, 03:33:54 AM »
thanks alex,

is it possible to implement an option to set the bounding box region by the imported shapes? would be great to only generate the mesh inside the shapes (for ortho surveys)

thanks

Pages: [1] 2