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.


Topics - B_Free42

Pages: [1]
1
Bug Reports / cudaMemGetInfo time out error
« on: January 25, 2020, 05:29:51 AM »
When I first run Build Dense Point Cloud on Medium or Low setting I get this error after several seconds:

cudaMemGetInfo(&free_mem_size, &total_mem_size): the launch timed out and was terminated (6) at line 211

When I try running the same thing again, it errors out almost immediately and gives the same error message except that it terminated at line 33.

The Build Dense Point Cloud process will finish if I run it on "Lowest" quality setting.

Is this something I can fix? Do I need to change the amount of time the computer waits for the time out? Thanks!

I'm running Windows 10 Home on Dell G7 7790 laptop. GPU is NVidia GeForce RTX 2080 with Max-Q Design.

2
General / "Incompatible Dense Cloud Colors" in chunk merge
« on: May 14, 2017, 02:24:38 AM »
I aligned two chunks already and now I'm trying to merge their dense clouds together. Every time I try the progress bar it gets all the way to the end and then I get a message box that says "Incompatible Dense Cloud Colors" and no merged chunk.

The two chunks are a front and back of a house. I couldn't get Photoscan to stitch all the photos into one model, so I separated them into a front and back chunk. The coloring should be similar if not the same since all photos were taken on the same day with the same camera.

Any ideas how to fix this?

3
General / Consistent system failure when filtering depth maps
« on: November 07, 2016, 01:04:07 AM »
I've tried to run
"Build Dense Cloud..."
Quality: High
Depth Filtering: Mild
on a project three times, and each time my computer has failed at the same point.

Any idea what might be causing the memory error and more importantly, how can I change my system to make it more likely to complete the Depth Map?

I was able to build a Dense Cloud using Quality: Medium, but didn't get the detail I wanted.

Here's the log from my last failure:
Quote
2016-11-06 13:39:52 [GPU] estimating 954x1071x160 disparity using 954x536x32f tiles, offset -40
2016-11-06 13:39:53 timings: rectify: 0.051 disparity: 0.715 borders: 0.022 filter: 0.043 fill: 0
2016-11-06 13:39:56 finished depth reconstruction in 63936.8 seconds
2016-11-06 13:39:56 Device 1 performance: 20.5473 million samples/sec (CPU)
2016-11-06 13:39:56 Device 2 performance: 44.024 million samples/sec (GeForce GTX 560 Ti)
2016-11-06 13:39:56 Total performance: 64.5713 million samples/sec
2016-11-06 13:39:56 Generating dense point cloud...
2016-11-06 13:40:14 selected 346 cameras in 17.85 sec
2016-11-06 13:40:14 working volume: 2150x1326x1451
2016-11-06 13:40:14 tiles: 1x1x1
2016-11-06 13:40:14 selected 346 cameras
2016-11-06 13:40:14 preloading data... done in 36.346 sec
2016-11-06 13:40:50 filtering depth maps...

The last log entry is 13:40:50 filtering depth maps...  and then the computer crashed at 1:52:41 pm. Each time the process failed this was the last entry in the Photoscan log.

Here's my system:
Intel Core i7-2600K @3.40 GHz, 3801 Mhz, 4 Cores, 8 Logical Processors
RAM: 24GB
64 bit, Windows 10
One GPU: NVidia GeForce GTX 560 Ti

The input is 423 tif photos - tif photos that were converted from RAW files. Each one is 6000 x 4000 pixels and about 70 Mb in size.

4
General / Generating Dense Points: Longer it runs the more time is left
« on: October 26, 2016, 04:46:30 AM »
Photoscan has been generating the dense point cloud for about 18 hours now. It is currently 2016-10-25 20:19:00 local time and the last entry in the Photoscan log is from this morning at 3:08. It says "filtering depth maps..."

Earlier this afternoon, the top progress bar indicated there was about 24 hours left.  Now, six hours later or so, it's telling me there is over 31 hours left. The longer I let Photoscan run the more time it says it has remaining. See attached screenshot from just now.

Is the program stuck in some kind of loop? Will it ever finish executing?  At this point should I cancel the dense point cloud generation? It's run for over 30 hours already, I'd hate to give up on it now. What's going on? Am I doing something wrong?

The input is 142 tif photos - tif photos that were converted from RAW files. Each one is 6000 x 4000 pixels and about 70 Mb in size. This is the second time I've tried generating a model with tif files - the first time I got memory error after some 30 hours.  Is there something I do to change this?

Here some excerpts from the log. Starting from when I first loaded the photos.

Quote
2016-10-24 09:10:25 Agisoft PhotoScan Version: 1.2.6 build 2834 (64 bit)
2016-10-24 09:10:25 OpenGL Vendor: NVIDIA Corporation
2016-10-24 09:10:25 OpenGL Renderer: GeForce GTX 560 Ti/PCIe/SSE2
2016-10-24 09:10:25 OpenGL Version: 4.5.0 NVIDIA 372.90
2016-10-24 09:10:25 Maximum Texture Size: 16384
2016-10-24 09:10:25 Quad Buffered Stereo: not enabled
2016-10-24 09:10:25 ARB_vertex_buffer_object: supported
2016-10-24 09:11:28 Loading photos...
2016-10-24 09:11:37 Finished processing in 8.942 sec (exit code 1)
2016-10-24 09:12:05 Detecting points...
2016-10-24 09:12:10 photo 1: 39936 points
2016-10-24 09:12:15 photo 2: 39936 points
...
2016-10-24 09:24:44 photo 142: 39935 points
2016-10-24 09:24:44 points detected in 758.89 sec
2016-10-24 09:24:44 Matching points...
2016-10-24 10:21:42 3218536 matches found in 3417.64 sec
2016-10-24 10:21:42 matches combined in 0.522 sec
2016-10-24 10:23:49 matches filtered in 126.273 sec
2016-10-24 10:23:49 setting point indices... 157705 done in 0.091 sec
2016-10-24 10:23:49 generated 157705 tie points, 4.19292 average projections
2016-10-24 10:23:49 removed 139456 multiple indices
2016-10-24 10:23:49 removed 152 tracks
2016-10-24 10:23:49 finished matching in 4303.51 sec
2016-10-24 10:23:49 selected 147632 tracks out of 157553 in 0.027 sec
2016-10-24 10:23:49 Estimating camera locations...
2016-10-24 10:23:49 processing block: 46 photos
2016-10-24 10:23:49 pair 66 and 67: 1 robust from 3073
2016-10-24 10:23:49 pair 9 and 115: 0 robust from 1968
2016-10-24 10:23:49 pair 5 and 6: 764 robust from 1920
...
2016-10-24 10:25:14 adding 6185 points, 4416 far (0.883977 threshold), 3998 inaccurate, 123 invisible, 132 weak
2016-10-24 10:25:14 optimized in 20.838 seconds
2016-10-24 10:25:15 coordinates applied in 0 sec
2016-10-24 10:25:15 Finished processing in 4389.16 sec (exit code 1)
...
2016-10-24 10:39:40 loaded project in 0.047 sec
2016-10-24 10:39:40 Finished processing in 0.047 sec (exit code 1)
2016-10-24 10:41:29 Using device: GeForce GTX 560 Ti, 8 compute units, 2048 MB global memory
2016-10-24 10:41:29   max work group size 1024
2016-10-24 10:41:29   max work item sizes [1024, 1024, 64]
2016-10-24 10:41:29   max mem alloc size 512 MB
2016-10-24 10:41:29 Initializing...
2016-10-24 10:41:29 initializing...
2016-10-24 10:41:29 selected 142 cameras from 142 in 0.37 sec
2016-10-24 10:41:29 Loading photos...
2016-10-24 10:43:36 loaded photos in 126.312 seconds
2016-10-24 10:43:36 Reconstructing depth...
2016-10-24 10:43:37 [GPU] estimating 4804x2588x1088 disparity using 801x863x8u tiles, offset -72
2016-10-24 10:43:38 [CPU] estimating 5360x3750x672 disparity using 1072x938x8u tiles, offset -426
2016-10-24 10:44:24 timings: rectify: 1.453 disparity: 45.745 borders: 0.264 filter: 1.188 fill: 0
...
2016-10-25 00:37:54 [GPU] estimating 4150x7351x768 disparity using 830x919x8u tiles, offset -240
2016-10-25 00:39:07 timings: rectify: 1.978 disparity: 71.401 borders: 0.317 filter: 1.586 fill: 0
2016-10-25 00:39:10 [GPU] estimating 5802x3733x1184 disparity using 829x934x8u tiles, offset -728
2016-10-25 00:41:08 timings: rectify: 1.16 disparity: 117.034 borders: 0.148 filter: 1.124 fill: 0
2016-10-25 00:41:10 [GPU] estimating 5705x3862x992 disparity using 951x773x8u tiles, offset -511
2016-10-25 00:42:17 timings: rectify: 1.184 disparity: 66.066 borders: 0.179 filter: 1.145 fill: 0
2016-10-25 00:42:20 [GPU] estimating 5574x3982x608 disparity using 929x797x8u tiles, offset -147
2016-10-25 00:43:05 timings: rectify: 1.175 disparity: 44.117 borders: 0.393 filter: 1.193 fill: 0
2016-10-25 00:43:08 [GPU] estimating 5490x3967x352 disparity using 915x794x8u tiles, offset 0
2016-10-25 00:43:39 timings: rectify: 1.164 disparity: 29.591 borders: 0.739 filter: 1.275 fill: 0
2016-10-25 00:43:50 finished depth reconstruction in 50414.8 seconds
2016-10-25 00:43:50 Device 1 performance: 100.008 million samples/sec (CPU)
2016-10-25 00:43:50 Device 2 performance: 264.061 million samples/sec (GeForce GTX 560 Ti)
2016-10-25 00:43:50 Total performance: 364.069 million samples/sec
2016-10-25 00:43:51 Generating dense point cloud...
2016-10-25 00:44:04 selected 142 cameras in 13.507 sec
2016-10-25 00:44:04 working volume: 11898x5618x6405
2016-10-25 00:44:04 tiles: 3x1x2
2016-10-25 00:44:04 selected 97 cameras
2016-10-25 00:44:04 preloading data... done in 45.04 sec
2016-10-25 00:44:49 filtering depth maps... done in 7978.17 sec
2016-10-25 02:57:53 preloading data... done in 415.672 sec
2016-10-25 03:04:48 accumulating data... done in 103.957 sec
2016-10-25 03:06:33 building point cloud... done in 0.516 sec
2016-10-25 03:06:36 selected 141 cameras
2016-10-25 03:06:36 preloading data... done in 85.767 sec
2016-10-25 03:08:01 filtering depth maps...

5
General / Out of Memory Error Recovery?
« on: October 22, 2016, 04:02:22 PM »
I was creating the Dense Point Cloud, it was over 90% finished after running for over 36 hours.
Here are the last few lines from the log file:
Quote
2016-10-22 00:02:10 [GPU] estimating 2008x2781x128 disparity using 670x927x8u tiles, offset -63
2016-10-22 00:02:13 timings: rectify: 0.293 disparity: 3.17 borders: 0.16 filter: 0.297 fill: 0
2016-10-22 00:02:24 finished depth reconstruction in 141101 seconds
2016-10-22 00:02:24 Device 1 performance: 96.1072 million samples/sec (CPU)
2016-10-22 00:02:24 Device 2 performance: 212.911 million samples/sec (GeForce GTX 560 Ti)
2016-10-22 00:02:24 Total performance: 309.018 million samples/sec
2016-10-22 00:02:26 Generating dense point cloud...
2016-10-22 00:08:59 selected 376 cameras in 393.231 sec
2016-10-22 00:08:59 working volume: 4614x3276x3541
2016-10-22 00:08:59 tiles: 1x1x1
2016-10-22 00:08:59 selected 376 cameras
2016-10-22 00:08:59 preloading data... Finished processing in 146206 sec (exit code 0)
2016-10-22 01:27:18 Error: bad allocation
There is a also new pagefile.sys file that's 72 Gigabytes.

Is there any way to recover the work that's already been done?  Otherwise, any idea how to prevent this error in the future?

Here's my system:
Windows 10, 64 bit
Intel Core i7-2600K
24 GB RAM
GeForce GTX 560 Ti

Pages: [1]