Messages

1

General / Re: Tweak to limit GPU load during dense cloud generation

« on: September 22, 2021, 09:33:56 PM »

Hello Pkroks,

Thank you for additional information.

We'll also try to use the 21H1 update for Windows 10 and see, if it causes any similar GPU-related processing problems.

Hi Alexey, it seems that the laptop in question is actually over heating. The actual hardware is working but the cooling is inefficient and the temp seems to get too high and it throttles back limiting the card use to then prevent any permanent damage.

I just replaced the thermal paste again with new stuff, cleaned out the vents and it processed on high settings.

Is there a way to limit the load on the card so it doesn't get to such high temps, understandably it would take longer to do processing, but I would limit the load until I can find a permanent or more efficient way to cool the laptop sufficiently.

temps on the card were getting up to max of 87C and sitting around 80C during depth maps.

Once it gives the error I have to restart the laptop to then try processing again.

2

General / Re: Tweak to limit GPU load during dense cloud generation

« on: August 30, 2021, 07:26:30 PM »

Hi Alexey, it seems it must be something wrong with my graphics card. I will replace the card and see if it fixes the problem.

Thanks

3

General / Re: Tweak to limit GPU load during dense cloud generation

« on: August 19, 2021, 12:01:13 AM »

Hi Alexey, I tried your tweek and switched it to OpenCL, it does the same and crashes the application.

All these problems only started when I installed the latest version of windows 10 pro with 21h1. I will attempt to roll this back.

I have also attempted using Reality capture to test and it is not working either, similar CUDA error. And unigene heaven tests are displaying artifacts and crashing. Hopefully rolling back to an earlier windows will help, otherwise it seems my GPU hardware may have freaked out..

will update you after I do a clean install with an older version of windows. It may be worth noting the errors also occur with both the Studio drivers and the Game ready drivers for Nvidia.

4

General / Re: Tweak to limit GPU load during dense cloud generation

« on: August 18, 2021, 12:20:36 AM »

Now it won't even complete alignment without crashing..

5

General / Re: Tweak to limit GPU load during dense cloud generation

« on: August 17, 2021, 10:27:38 PM »

Hi Alexey,

System specs -
Intel i7 8700k 3.70ghz 6cores
Nvidia GTX 1070 8gb ddr5
32gb RAM
samsung 850 evo 250gb ssd, and 1tb SSHD

Nvidia drivers version 471.68 installed off the nvidia downloads page. clean install after using Guru3d DDU uninstaller to clean previous versions.
Windows 10 profession 21H1 (build 19043.1165)

Error as shown in agisoft Logfile

2021-08-17 08:47:01 [GPU 1] Camera 110 tile #1/2: level #5/5 (x2 downscale: 1248x1824, image blowup: 2496x3648) done in 1.527 s = 33% propagation + 52% refinement + 8% filtering + 0% smoothing
2021-08-17 08:47:05 [GPU 1] Camera 110 samples after final filtering: 86% = 100% - 0% (not matched) - 5% (bad matched) - 0% (no neighbors) - 0% (no cost neighbors) - 7% (inconsistent normal) - 0% (estimated bad angle) - 0% (found bad angle) - 2% (speckles filtering)
2021-08-17 08:47:05 [GPU 1] Camera 110 tile #2/2: level #5/5 (x2 downscale: 1248x1824, image blowup: 2496x3648) done in 1.838 s = 32% propagation + 55% refinement + 7% filtering + 0% smoothing
2021-08-17 08:47:05 [GPU 1] group 1/1: estimating depth map for 25/49 camera 111 (30 neighbs)...
2021-08-17 08:47:08 [GPU 1] Camera 111 samples after final filtering: 70% = 100% - 0% (not matched) - 10% (bad matched) - 1% (no neighbors) - 2% (no cost neighbors) - 11% (inconsistent normal) - 0% (estimated bad angle) - 0% (found bad angle) - 5% (speckles filtering)
2021-08-17 08:47:08 [GPU 1] Camera 111 tile #1/2: level #5/5 (x2 downscale: 1248x1824, image blowup: 2496x3648) done in 1.519 s = 33% propagation + 52% refinement + 8% filtering + 0% smoothing
2021-08-17 08:47:12 [GPU 1] Camera 111 samples after final filtering: 83% = 100% - 0% (not matched) - 5% (bad matched) - 0% (no neighbors) - 0% (no cost neighbors) - 8% (inconsistent normal) - 0% (estimated bad angle) - 0% (found bad angle) - 2% (speckles filtering)
2021-08-17 08:47:12 [GPU 1] Camera 111 tile #2/2: level #5/5 (x2 downscale: 1248x1824, image blowup: 2496x3648) done in 1.812 s = 32% propagation + 54% refinement + 7% filtering + 0% smoothing
2021-08-17 08:47:12 [GPU 1] group 1/1: estimating depth map for 26/49 camera 112 (29 neighbs)...
2021-08-17 08:47:14 Error: cudaDestroySurfaceObject(cu_surface_): misaligned address (74) at line 126
2021-08-17 08:47:14 Warning: cudaStreamDestroy failed: misaligned address (74)
2021-08-17 08:47:15 Finished processing in 209.247 sec (exit code 0)
2021-08-17 08:47:15 Error: Kernel failed: misaligned address (74) at line 308

6

General / Tweak to limit GPU load during dense cloud generation

« on: August 17, 2021, 04:26:26 PM »

Hi,

I am struggling to complete processing and seem to have an issue when I try to do processing on High or higher settings. Medium completes in no time..

I remember reading there is a tweak parameter that can be used in the preferences to limit the load placed on the GPU and CUDA cores to help the system to complete; it takes a bit longer but the load isn't that high.

I have previously had issues with this laptop of mine - I have reinstalled the latest Nvidia drivers from the nvidia website directly. I have also updated all windows and Agisoft and as of the last ten days or so I cannot complete any processing on High settings.

Any help is appreciated.

7

General / Re: Sorting out DJI's bad GPS Altitude tagging

« on: April 25, 2019, 08:34:42 PM »

This may be the wrong place, but I am having an issue with data I have processed, an issue I have never come across before but it may be exactly related to the DJI method of recording GPS and altitude.

I have processed an area flown with a DJI Phantom 4 Pro.

The GCPS were captured and recorded. Their values have been used for processing.

The final output model seems to be off uniformly approximately 10m.

For example -

GCP7 - elevation is 1238m
The actual elevation of the output model at the GCP7 location is 1228m.

GCP8 is 1241m
The actual elevation of the output model at the GCP8 location is 1231m.

I am unsure how there is this variation across the site, I have never experienced this before? How do I correct the error?

8

Bug Reports / Re: Cuda stream destroy failed unknown error (win10 pro)

« on: March 20, 2019, 09:19:32 AM »

So here's an update what I have done.

Tried to install latest drivers. Failed cudastream
Install older driver. Failed
Installed older windows with older drivers. Failed
Installed older windows with new drivers. Failed
Installed old photoscan version. Failed
Tried opencl instead if cuda. Failed.

Then tried some test on my hardware.
Unigine heaven extreme. Passed.
Pass mark burn in. Passed
Pass mark burn in on 100% passed
Memtest86 passed

I took the back off the laptop and replaced thermal pads and thermal paste. Hardly any difference. Still failing on processing.

Tried to process using pix4d on normal.settings. Cuda failed.
Tried to process in pix4d but limited resources to 24gb of ram and 10 CPU threads. Passed

But I don't have a full pix4d license to be able to export any data.

Any ideas? Could it just be that it has been overheating and changing the thermal pads and paste has reduced it by maybe 2 degrees and so not overheating? Would limiting resources to less than max then reduce load and overall temps?

I have also just had a BSOD - kernel mode trap... The dump file indicates the cause of the problem to be the nVidia driver - which is the latest as per nVidias website.

9

Bug Reports / Re: Cuda stream destroy failed unknown error (win10 pro)

« on: March 19, 2019, 01:37:29 PM »

Is there a setting or console input in agisoft to limit the resources it uses? Pix4d you can select to use only a portion of available resources.

Perhaps there is a similar command or setting in agisoft? I ask because pix4 has completed the cloud generation with only 80% if computer resources. So perhaps I can do the same with agisoft

10

Bug Reports / Re: Cuda stream destroy failed unknown error (win10 pro)

« on: March 19, 2019, 12:25:33 AM »

Hello Pkroks,

I see that you have issues both with OpenCL and CUDA implementation.

I'll see, if we have some ideas regarding this report.

Please do. I have previously processed this entire data set with no issues on both AGISOFT and PIX4D. Now it seems something has gone wrong and my system is unstable as both PIX4D and AGISOFT are crashing now since this latest update.

I also had an epiphany that perhaps it was to do with voltage supply - I live in Africa and sometimes we have issues with low voltage; I put a voltage regulator on and plugged the laptop into that; seems it helped and it was a lot more stable. Got to 94% of the mesh and depth map creation before it gave me this error:

2019-03-18 20:15:36 [CPU 2]   Updating result...
2019-03-18 20:15:37 [CPU 2] Part done in 62.379 sec
2019-03-18 20:15:37 [CPU 2] 1 Parts 295-295/295...
2019-03-18 20:15:37 [CPU 2]   Initializing octree...
2019-03-18 20:15:37 [CPU 2]   Initializing histograms...
2019-03-18 20:15:41 [CPU 2]   Initializing...
2019-03-18 20:15:42 [CPU 2]   Iterating...
2019-03-18 20:15:52 [CPU 2]   Updating result...
2019-03-18 20:15:53 [CPU 2] Part done in 15.996 sec
2019-03-18 20:15:53 Finished processing in 4262.08 sec (exit code 0)
2019-03-18 20:15:53 Error: Kernel failed: unknown error (30) at line 106
2019-03-18 20:19:44 SaveProject: path = C:/PROJECTS/Embassy HIGH.psx
2019-03-18 20:19:44 Saving project...
2019-03-18 20:19:44 saved project in 0.09 sec
2019-03-18 20:19:44 Finished processing in 0.09 sec (exit code 1)
2019-03-18 20:19:54 Estimating resolution...
2019-03-18 20:19:54 Estimating point cloud resolution...
2019-03-18 20:19:54 Finished processing in 0.186 sec (exit code 1)


I then tried again on the usual HIGH settings and it got to 75% and gave me


2019-03-18 20:43:12 timings: rectify: 0.032 disparity: 0.79 borders: 0.046 filter: 0.145 fill: 0
2019-03-18 20:43:12 [GPU] estimating 2175x1720x480 disparity using 1088x896x8u tiles
2019-03-18 20:43:15 Error: Kernel failed: unknown error (30) at line 115
2019-03-18 20:43:15 GPU processing failed, switching to CPU mode
2019-03-18 20:43:15 [CPU] estimating 2175x1720x480 disparity using 1088x860x8u tiles
2019-03-18 20:43:18 timings: rectify: 0.204 disparity: 6.263 borders: 0.232 filter: 0.353 fill: 0
2019-03-18 20:43:21
2019-03-18 20:43:21 Depth reconstruction devices performance:
2019-03-18 20:43:21  - 5%    done by CPU
2019-03-18 20:43:21  - 95%    done by GeForce GTX 1070
2019-03-18 20:43:21 Total time: 133.407 seconds
2019-03-18 20:43:21
2019-03-18 20:43:21 Warning: cudaStreamDestroy failed: unknown error (30)
2019-03-18 20:43:21 Warning: cudaStreamDestroy failed: unknown error (30)
2019-03-18 20:43:21 Finished processing in 608.628 sec (exit code 0)
2019-03-18 20:43:21 Error: unknown error (30) at line 211




I previously succeeded in processing this data set using point cloud - but wanted to do it using the depth maps and see if what the result was. Now I can't even complete the point cloud processing again?



Could it be that my hardware is somehow faulty now? I have been trying to run UNIGINE HEAVEN to benchmark and test the GPU and CPU and see if it is stable; along with also trying MSI KOMBUSTOR. They both appear stable but the laptop is running hot?

Perhaps it is overheating? I'm really lost as to what would have changed between last week and this week and a new windows upgrade.

11

Bug Reports / Re: Cuda stream destroy failed unknown error (win10 pro)

« on: March 18, 2019, 07:46:47 PM »

Hello Pkroks,

Does the image matching process (first phase of the Align Photos operation) performs well using GPU?

Hi Alexey, Yes I believe so. Image Alignment on High completes without issue and is quick. Maybe 10 minutes (281 photos).


I have just formatted the laptop, and reinstalled windows 10 pro. Installed latest drivers from manufacturer and the latest nVidia graphics driver from nVidia.

As per Agisoft support I tried to use the latest nvidia driver, and then process depth maps and monitor the RAM usage. PC ram usage never went above 4gb (out of 32gb). And then dedicated GPU Ram usage never went above 2.3gb out of 8gb (it didn't even use any shared GPU memory)


I then attempted to use a tweak and activate OPEN CL instead of CUDA.

Began processing - and it gave me a new error - out of resources.

2019-03-18 16:49:23 using CPU implementation...
2019-03-18 16:49:23 GPU depth map warping failed: CL_OUT_OF_RESOURCES (-5) at line 355
2019-03-18 16:49:23 using CPU implementation...
2019-03-18 16:49:23 GPU depth map warping failed: CL_OUT_OF_RESOURCES (-5) at line 355
2019-03-18 16:49:23 using CPU implementation...
2019-03-18 16:49:23 GPU depth map warping failed: CL_OUT_OF_RESOURCES (-5) at line 355
2019-03-18 16:49:23 using CPU implementation...
2019-03-18 16:49:23 GPU depth map warping failed: CL_OUT_OF_RESOURCES (-5) at line 355
2019-03-18 16:49:23 using CPU implementation...
2019-03-18 16:49:23 GPU depth map warping failed: CL_OUT_OF_RESOURCES (-5) at line 355
2019-03-18 16:49:23 using CPU implementation...
2019-03-18 16:49:24 GPU depth map warping failed: CL_OUT_OF_RESOURCES (-5) at line 355
2019-03-18 16:49:24 using CPU implementation...
2019-03-18 16:49:24 GPU depth map warping failed: CL_OUT_OF_RESOURCES (-5) at line 355
2019-03-18 16:49:24 using CPU implementation...
2019-03-18 16:49:24 GPU depth map warping failed: CL_OUT_OF_RESOURCES (-5) at line 355
2019-03-18 16:49:24 using CPU implementation...
2019-03-18 16:49:24 GPU depth map warping failed: CL_OUT_OF_RESOURCES (-5) at line 355
2019-03-18 16:49:24 using CPU implementation...
2019-03-18 16:49:24 GPU depth map warping failed: CL_OUT_OF_RESOURCES (-5) at line 355
2019-03-18 16:49:24 using CPU implementation...
2019-03-18 16:49:24 GPU depth map warping failed: CL_OUT_OF_RESOURCES (-5) at line 355
2019-03-18 16:49:24 using CPU implementation...
2019-03-18 16:49:24 GPU depth map warping failed: CL_OUT_OF_RESOURCES (-5) at line 355
2019-03-18 16:49:24 using CPU implementation...
2019-03-18 16:49:24 GPU depth map warping failed: CL_OUT_OF_RESOURCES (-5) at line 355
2019-03-18 16:49:24 using CPU implementation...
2019-03-18 16:49:24 GPU depth map warping failed: CL_OUT_OF_RESOURCES (-5) at line 355
2019-03-18 16:49:24 using CPU implementation...
2019-03-18 16:49:24 GPU depth map warping failed: CL_OUT_OF_RESOURCES (-5) at line 355
2019-03-18 16:49:24 using CPU implementation...
2019-03-18 16:49:24 GPU depth map warping failed: CL_OUT_OF_RESOURCES (-5) at line 355
2019-03-18 16:49:24 using CPU implementation...
2019-03-18 16:49:24 GPU depth map warping failed: CL_OUT_OF_RESOURCES (-5) at line 355
2019-03-18 16:49:24 using CPU implementation...
2019-03-18 16:49:24 GPU depth map warping failed: CL_OUT_OF_RESOURCES (-5) at line 355
2019-03-18 16:49:24 using CPU implementation...
2019-03-18 16:49:24 GPU depth map warping failed: CL_OUT_OF_RESOURCES (-5) at line 355
2019-03-18 16:49:24 using CPU implementation...
2019-03-18 16:49:24 GPU depth map warping failed: CL_OUT_OF_RESOURCES (-5) at line 355
2019-03-18 16:49:24 using CPU implementation...
2019-03-18 16:49:24 GPU depth map warping failed: CL_OUT_OF_RESOURCES (-5) at line 355
2019-03-18 16:49:24 using CPU implementation...
2019-03-18 16:49:24 GPU depth map warping failed: CL_OUT_OF_RESOURCES (-5) at line 355
2019-03-18 16:49:24 using CPU implementation...
2019-03-18 16:49:24 GPU depth map warping failed: CL_OUT_OF_RESOURCES (-5) at line 355
2019-03-18 16:49:24 using CPU implementation...
2019-03-18 16:49:24 GPU depth map warping failed: CL_OUT_OF_RESOURCES (-5) at line 355
2019-03-18 16:49:24 using CPU implementation...
2019-03-18 16:49:24 GPU depth map warping failed: CL_OUT_OF_RESOURCES (-5) at line 355
2019-03-18 16:49:24 using CPU implementation...
2019-03-18 16:49:24 GPU depth map warping failed: CL_OUT_OF_RESOURCES (-5) at line 355
2019-03-18 16:49:24 using CPU implementation...
2019-03-18 16:49:24 GPU depth map warping failed: CL_OUT_OF_RESOURCES (-5) at line 355
2019-03-18 16:49:24 using CPU implementation...
2019-03-18 16:49:24 GPU depth map warping failed: CL_OUT_OF_RESOURCES (-5) at line 355
2019-03-18 16:49:24 using CPU implementation...
2019-03-18 16:49:24 GPU depth map warping failed: CL_OUT_OF_RESOURCES (-5) at line 355
2019-03-18 16:49:24 using CPU implementation...
2019-03-18 16:49:24 GPU depth map warping failed: CL_OUT_OF_RESOURCES (-5) at line 355
2019-03-18 16:49:24 using CPU implementation...
2019-03-18 16:49:24 GPU depth map warping failed: CL_OUT_OF_RESOURCES (-5) at line 355
2019-03-18 16:49:24 using CPU implementation...
2019-03-18 16:49:24 GPU depth map warping failed: CL_OUT_OF_RESOURCES (-5) at line 355
2019-03-18 16:49:24 using CPU implementation...
2019-03-18 16:49:24 GPU depth map warping failed: CL_OUT_OF_RESOURCES (-5) at line 355
2019-03-18 16:49:24 using CPU implementation...
2019-03-18 16:49:24 GPU depth map warping failed: CL_OUT_OF_RESOURCES (-5) at line 355
2019-03-18 16:49:24 using CPU implementation...
2019-03-18 16:49:25 GPU depth map warping failed: CL_OUT_OF_RESOURCES (-5) at line 355
2019-03-18 16:49:25 using CPU implementation...
2019-03-18 16:49:25 GPU depth map warping failed: CL_OUT_OF_RESOURCES (-5) at line 355
2019-03-18 16:49:25 using CPU implementation...
2019-03-18 16:49:25 GPU depth map warping failed: CL_OUT_OF_RESOURCES (-5) at line 355
2019-03-18 16:49:25 using CPU implementation...
2019-03-18 16:49:25 GPU depth map warping failed: CL_OUT_OF_RESOURCES (-5) at line 355
2019-03-18 16:49:25 using CPU implementation...
2019-03-18 16:49:25 GPU depth map warping failed: CL_OUT_OF_RESOURCES (-5) at line 355
2019-03-18 16:49:25 using CPU implementation...
2019-03-18 16:49:25 GPU depth map warping failed: CL_OUT_OF_RESOURCES (-5) at line 355
2019-03-18 16:49:25 using CPU implementation...
2019-03-18 16:49:25 GPU depth map warping failed: CL_OUT_OF_RESOURCES (-5) at line 355
2019-03-18 16:49:25 using CPU implementation...
2019-03-18 16:49:25 GPU depth map warping failed: CL_OUT_OF_RESOURCES (-5) at line 355
2019-03-18 16:49:25 using CPU implementation...
2019-03-18 16:49:25 GPU depth map warping failed: CL_OUT_OF_RESOURCES (-5) at line 355
2019-03-18 16:49:25 using CPU implementation...
2019-03-18 16:49:25 GPU depth map warping failed: CL_OUT_OF_RESOURCES (-5) at line 355
2019-03-18 16:49:25 using CPU implementation...
2019-03-18 16:49:25 GPU depth map warping failed: CL_OUT_OF_RESOURCES (-5) at line 355
2019-03-18 16:49:25 using CPU implementation...
2019-03-18 16:49:25 GPU depth map warping failed: CL_OUT_OF_RESOURCES (-5) at line 355
2019-03-18 16:49:25 using CPU implementation...
2019-03-18 16:49:25 GPU depth map warping failed: CL_OUT_OF_RESOURCES (-5) at line 355
2019-03-18 16:49:25 using CPU implementation...
2019-03-18 16:49:25 GPU depth map warping failed: CL_OUT_OF_RESOURCES (-5) at line 355
2019-03-18 16:49:25 using CPU implementation...
2019-03-18 16:49:25 GPU depth map warping failed: CL_OUT_OF_RESOURCES (-5) at line 355
2019-03-18 16:49:25 using CPU implementation...
2019-03-18 16:49:25 GPU depth map warping failed: CL_OUT_OF_RESOURCES (-5) at line 355
2019-03-18 16:49:25 using CPU implementation...
2019-03-18 16:49:25 GPU depth map warping failed: CL_OUT_OF_RESOURCES (-5) at line 355
2019-03-18 16:49:25 using CPU implementation...
2019-03-18 16:49:25 GPU depth map warping failed: CL_OUT_OF_RESOURCES (-5) at line 355
2019-03-18 16:49:25 using CPU implementation...
2019-03-18 16:49:25 GPU depth map warping failed: CL_OUT_OF_RESOURCES (-5) at line 355
2019-03-18 16:49:25 using CPU implementation...
2019-03-18 16:49:25 GPU depth map warping failed: CL_OUT_OF_RESOURCES (-5) at line 355
2019-03-18 16:49:25 using CPU implementation...
2019-03-18 16:49:25 GPU depth map warping failed: CL_OUT_OF_RESOURCES (-5) at line 355
2019-03-18 16:49:25 using CPU implementation...
2019-03-18 16:49:25 GPU depth map warping failed: CL_OUT_OF_RESOURCES (-5) at line 355
2019-03-18 16:49:25 using CPU implementation...
2019-03-18 16:49:25 GPU depth map warping failed: CL_OUT_OF_RESOURCES (-5) at line 355
2019-03-18 16:49:25 using CPU implementation...
2019-03-18 16:49:25 GPU depth map warping failed: CL_OUT_OF_RESOURCES (-5) at line 355
2019-03-18 16:49:25 using CPU implementation...
2019-03-18 16:49:25 GPU depth map warping failed: CL_OUT_OF_RESOURCES (-5) at line 355
2019-03-18 16:49:25 using CPU implementation...
2019-03-18 16:49:26 GPU depth map warping failed: CL_OUT_OF_RESOURCES (-5) at line 355
2019-03-18 16:49:26 using CPU implementation...
2019-03-18 16:49:26 GPU depth map warping failed: CL_OUT_OF_RESOURCES (-5) at line 355
2019-03-18 16:49:26 using CPU implementation...
2019-03-18 16:49:26 GPU depth map warping failed: CL_OUT_OF_RESOURCES (-5) at line 355
2019-03-18 16:49:26 using CPU implementation...
2019-03-18 16:49:26 GPU depth map warping failed: CL_OUT_OF_RESOURCES (-5) at line 355
2019-03-18 16:49:26 using CPU implementation...
2019-03-18 16:49:26 GPU depth map warping failed: CL_OUT_OF_RESOURCES (-5) at line 355
2019-03-18 16:49:26 using CPU implementation...
2019-03-18 16:49:26 GPU depth map warping failed: CL_OUT_OF_RESOURCES (-5) at line 355
2019-03-18 16:49:26 using CPU implementation...
2019-03-18 16:49:26 GPU depth map warping failed: CL_OUT_OF_RESOURCES (-5) at line 355
2019-03-18 16:49:26 using CPU implementation...
2019-03-18 16:49:26 GPU depth map warping failed: CL_OUT_OF_RESOURCES (-5) at line 355
2019-03-18 16:49:26 using CPU implementation...
2019-03-18 16:49:26 GPU depth map warping failed: CL_OUT_OF_RESOURCES (-5) at line 355
2019-03-18 16:49:26 using CPU implementation...
2019-03-18 16:49:26 GPU depth map warping failed: CL_OUT_OF_RESOURCES (-5) at line 355
2019-03-18 16:49:26 using CPU implementation...
2019-03-18 16:49:26 GPU depth map warping failed: CL_OUT_OF_RESOURCES (-5) at line 355
2019-03-18 16:49:26 using CPU implementation...
2019-03-18 16:49:26 GPU depth map warping failed: CL_OUT_OF_RESOURCES (-5) at line 355
2019-03-18 16:49:26 using CPU implementation...
2019-03-18 16:49:26 GPU depth map warping failed: CL_OUT_OF_RESOURCES (-5) at line 355
2019-03-18 16:49:26 using CPU implementation...
2019-03-18 16:49:26 GPU depth map warping failed: CL_OUT_OF_RESOURCES (-5) at line 355
2019-03-18 16:49:26 using CPU implementation...
2019-03-18 16:49:26 GPU depth map warping failed: CL_OUT_OF_RESOURCES (-5) at line 355
2019-03-18 16:49:26 using CPU implementation...
2019-03-18 16:49:26 GPU depth map warping failed: CL_OUT_OF_RESOURCES (-5) at line 355
2019-03-18 16:49:26 using CPU implementation...
2019-03-18 16:49:26 GPU depth map warping failed: CL_OUT_OF_RESOURCES (-5) at line 355
2019-03-18 16:49:26 using CPU implementation...
2019-03-18 16:49:26 GPU depth map warping failed: CL_OUT_OF_RESOURCES (-5) at line 355
2019-03-18 16:49:26 using CPU implementation...
2019-03-18 16:49:26 GPU depth map warping failed: CL_OUT_OF_RESOURCES (-5) at line 355
2019-03-18 16:49:26 using CPU implementation...
2019-03-18 16:49:29
2019-03-18 16:49:29 Depth reconstruction devices performance:
2019-03-18 16:49:29  - 10%    done by CPU
2019-03-18 16:49:29  - 90%    done by GeForce GTX 1070
2019-03-18 16:49:29 Total time: 260.116 seconds
2019-03-18 16:49:29 CPU fallbacks: 43
2019-03-18 16:49:29
2019-03-18 16:49:29 19 depth maps generated in 262.908 sec
2019-03-18 16:49:29 saved depth maps block in 0.161 sec
2019-03-18 16:49:29 loaded depth map partition in 0 sec
2019-03-18 16:49:29 Initializing...
2019-03-18 16:49:29 Using device: GeForce GTX 1070, 16 compute units, 8192 MB global memory, OpenCL 1.2
2019-03-18 16:49:29   driver version: 419.35, platform version: OpenCL 1.2 CUDA 10.1.120
2019-03-18 16:49:29   max work group size 1024
2019-03-18 16:49:29   max work item sizes [1024, 1024, 64]
2019-03-18 16:49:29   max mem alloc size 2048 MB
2019-03-18 16:49:29   warp size 32
2019-03-18 16:49:29 Error: CL_OUT_OF_RESOURCES (-5) at line 211
2019-03-18 16:49:29 Saving project...
2019-03-18 16:49:29 saved project in 0 sec
2019-03-18 16:49:29 Finished batch processing in 506.592 sec (exit code 1)
>>>

12

Bug Reports / Re: Cuda stream destroy failed unknown error (win10 pro)

« on: March 17, 2019, 02:10:02 AM »

I have tried to disable 'Use CPU when performing GPU accelerated processing' and i begin the depth maps processing and get the following:

2019-03-17 01:07:57 BuildModel: source data = Depth maps, surface type = Height field, quality = High, depth filtering = Mild, face count = High, smoothness = Low, vertex colors = 1
2019-03-17 01:07:57 Generating depth maps...
2019-03-17 01:07:57 Initializing...
2019-03-17 01:07:57 sorting point cloud... done in 0.083 sec
2019-03-17 01:07:58 processing matches... done in 0.06 sec
2019-03-17 01:07:58 initializing...
2019-03-17 01:07:58 selected 281 cameras from 281 in 0.742 sec
2019-03-17 01:07:58 groups: 18 19 19 18 19 19 19 18 19 19 19 18 19 19 19
2019-03-17 01:07:58 845 of 281 used (300.712%)
2019-03-17 01:07:58 scheduled 15 depth map groups
2019-03-17 01:07:58 saved depth map partition in 0.006 sec
2019-03-17 01:07:58 loaded depth map partition in 0 sec
2019-03-17 01:07:58 Initializing...
2019-03-17 01:07:58 Error: unknown error (30) at line 33
2019-03-17 01:07:58 Finished batch processing in 0.9 sec (exit code 1)
>>>

13

Bug Reports / Cuda stream destroy failed unknown error (win10 pro)

« on: March 17, 2019, 12:47:12 AM »

Hi,

I have just updated my windows 64 bit to

windows pro version 1809 (build 17763.379)
nvidia gtx 1070 with driver version 419.35

agisoft metashape version 1.5.1 build 7618

I try to build the depth maps using CUDA enabled card and it gives me the error:

2019-03-16 23:33:38 GPU depth map warping failed: unknown error (30) at line 179
2019-03-16 23:33:38 using CPU implementation...
2019-03-16 23:33:41 Error: Kernel failed: unknown error (30) at line 115
2019-03-16 23:33:41 GPU processing failed, switching to CPU mode
2019-03-16 23:33:41 [CPU] estimating 994x1321x128 disparity using 994x1321x8u tiles
2019-03-16 23:33:42
2019-03-16 23:33:42 Depth reconstruction devices performance:
2019-03-16 23:33:42  - 5%    done by CPU
2019-03-16 23:33:42  - 95%    done by GeForce GTX 1070
2019-03-16 23:33:42 Total time: 85.324 seconds
2019-03-16 23:33:42
2019-03-16 23:33:42 Warning: cudaStreamDestroy failed: unknown error (30)
2019-03-16 23:33:42 Warning: cudaStreamDestroy failed: unknown error (30)
2019-03-16 23:33:42 Error: unknown error (30) at line 211
2019-03-16 23:33:42 Saving project...
2019-03-16 23:33:42 saved project in 0 sec
2019-03-16 23:33:42 Finished batch processing in 327.745 sec (exit code 1)
>>>




I have tried to roll back the nvidia drivers to versions 397.64 and even back to 385 where I had no issues, but then I get a different error message - I try to enable to CUDA graphics in preferences and it brings up the following entry:

the procedure entry point fatBinaryCTl_creathandle could not be located in the dynamic link library c:\\windows\system32\driverstore\filerepository\nvcvi.inf_amd64_3c5b42cdad4fff4f\nvopencl64.dll




any advice or work arounds to get it working would be appreciated. thanks

14

General / Re: Tree/plant counting

« on: October 30, 2018, 10:13:12 AM »

What kind of dataset do you have? images or point cloud? If you want to count crops, neural network based on images will be a good choice. If you want to count trees, tree top detection algorithms are common in many literatures based canopy height model derived from point cloud.

Hi Leonardo,

I have both the images and point cloud data.

I would like to count crops such as maize and tobacco.

And trees such as orange trees and other fruit trees.

Any more information you can provide would be much appreciated.

Thanks

15

General / Tree/plant counting

« on: October 27, 2018, 03:34:29 PM »

Hi everyone,

Simple question that may have a simple answer - what does everyone use to count crops/trees/plants? Does agisoft photoscan do this? If yes please could you point me in the right direction.

Many thanks