Messages

76

Bug Reports / Application calling GLX 1.3 function "glXCreatePbuffer" when GLX 1.3 is not supp

« on: September 11, 2017, 06:26:24 PM »

I am receiving the following error when I run the program. What does it mean?

[user@machine ~]$ numactl --interleave=all /usr/local/photoscan-pro_1_3_1/photoscan.sh&
[3] 134710
[2]   Exit 1                  numactl --interleave=all agisoft
[user@machine ~]$ failed to get the current screen resources
The license has expired.
WARNING: Application calling GLX 1.3 function "glXCreatePbuffer" when GLX 1.3 is not supported!  This is an application bug!
QXcbConnection: XCB error: 172 (Unknown), sequence: 169, resource id: 140, major code: 149 (Unknown), minor code: 20
QXcbConnection: XCB error: 1 (BadRequest), sequence: 626, resource id: 140, major code: 149 (Unknown), minor code: 25

77

General / Is GPU required to run 'align photos' quickly?

« on: September 11, 2017, 06:20:21 PM »

I am running align photos on a 200 photo chunk on a linux machine with 750gb memory.
It is taking 90 seconds/photo.

I noticed it does not have a GPU showing under the GPU tab in 1.3.1. Is this required to make align photos run more quickly? On my laptop, which is much less powerful but has a gpu, I am able to process the same set of images with about 3 seconds/photo.

78

General / Re: Align Cameras for Aerial Imagery - 5 hours for 200 images with 750GB memory?

« on: September 11, 2017, 06:15:45 PM »

I am still not having any luck getting the linux machine to run faster. Occasionally 20 seconds/photo, usually 90 seconds/photo.

I realize now that the linux machine does not have a GPU. Would this account for the align photos step being so slow?

79

General / Resume Build Orthomosaic for crashed operation (1.3.2.) ?

« on: May 26, 2017, 06:06:43 AM »

Is it possible to resume an operation that crashed? My connection to the photos I was orthomosaicing timed out in the middle of a 4 hour process and I don't want to start all over.

Here's some excerpts from the log, it's clear many parts of the operation completed without any issue:

2017-05-25 16:48:45 BuildOrthomosaic: projection type = Geographic, projection = WGS 84, surface = Mesh, blending mode = Mosaic, pixel size = 2.90036e-007 x 2.76802e-007
2017-05-25 16:48:45 Analyzing mesh...
2017-05-25 16:48:45 tessellating mesh... done (4068 -> 4074 faces)
2017-05-25 16:48:45 generating 300888x400178 orthophoto (13 levels, 0 resolution)
2017-05-25 16:48:45 selected 119 cameras
2017-05-25 16:48:45 Orthorectifying images...
2017-05-25 16:48:45 Orthorectifying 119 images
2017-05-25 16:49:21 5716.jpg: 11569x10298 -> 10665x4209
2017-05-25 16:49:50 5717.jpg: 13463x16403 -> 11266x9009
2017-05-25 16:49:52 5718.jpg: 14066x20460 -> 11367x8896
[...]
2017-05-25 19:34:05 Finished orthorectification in 9919.83 sec
2017-05-25 19:34:06 selected 397 tiles
2017-05-25 19:34:06 selected 397 tiles
2017-05-25 19:34:06 Updating partition...
2017-05-25 19:34:06 2 of 2 processed in 0.877 sec
2017-05-25 19:34:10 4 of 4 processed in 2.876 sec
[...]
2017-05-25 19:52:40 partition updated in 1114.38 sec
2017-05-25 19:52:40 selected 397 tiles
2017-05-25 19:52:40 Updating orthomosaic...
2017-05-25 19:52:44 loaded partition in 4.399 sec
2017-05-25 19:52:44 boundaries extracted in 0.05 sec
2017-05-25 19:52:45 0 images blended in 0.991 sec
2017-05-25 19:52:51 loaded partition in 3.933 sec
2017-05-25 19:52:51 boundaries extracted in 0.061 sec
2017-05-25 19:52:59 3 images blended in 7.766 sec
[...]
2017-05-25 20:47:52 Finished processing in 14346.5 sec (exit code 0)
2017-05-25 20:47:52 Error: Can't open tile: G:/path/to/myproject/myproject.files/0/0/orthomosaic/tile-9-85.tif

80

General / Re: Align Cameras for Aerial Imagery - 5 hours for 200 images with 750GB memory?

« on: May 25, 2017, 01:32:29 AM »

Trying again on the same machine, with 1.3.1., with the license activated. Now a chunk of the same 100 photos is taking 1:10 minutes per photo...I don't think I've changed anything, I don't get it.
The only difference this time is that I have a saved project I am working with.

-------------

I tried again just as I did in the previous post, a new project, didn't save, load the photos, add reference, and click Align Photos with only 'reference' preselection. Still 1:10. So it wasn't the fact that I had a saved project that was making it behave differently.

I will keep trying things out...

--------------------

Double-checked on my Windows machine (a laptop with much worse specs than the original Linux machine). I am able to run it on 100 photos, 1.3.1 pro trial version, about 15-20 seconds per photo.

-------------------

Activated the same trial license on my Windows machine that was used for the Linux machine. Still only 15-20 seconds per photo.

-------------------

81

General / Re: Align Cameras for Aerial Imagery - 5 hours for 200 images with 750GB memory?

« on: May 24, 2017, 07:00:53 PM »

Now I am trying on the original machine again, with PhotoScan Pro Demo 1.3.1 (it was the one installed).

A set of 100 images is taking about 20 seconds per image, so still much much faster than with 1.2.4.


Was there a big change between the two version that would explain this?

82

General / Re: Align Cameras for Aerial Imagery - 5 hours for 200 images with 750GB memory?

« on: May 24, 2017, 06:37:25 PM »

Well well....

It is running on the Windows 7 machine now with a 200 photo chunk taking about 15 seconds for each photo.

So something must be going very wrong on my other machine?

83

General / Re: Align Cameras for Aerial Imagery - 5 hours for 200 images with 750GB memory?

« on: May 24, 2017, 06:28:57 PM »

Here is results of aligning cameras with only 10 photos on PhotoScan 1.3.2 on the Windows 7 machine. Much faster. I will test again with 200 photos and see how that does:

2017-05-24 11:22:23 AlignPhotos: accuracy = High, preselection = reference, keypoint limit = 40000, tiepoint limit = 4000, constrain features by mask = 0, adaptive fitting = 1
2017-05-24 11:22:23 Detecting points...
2017-05-24 11:22:51 [CPU] photo 0: 40000 points
2017-05-24 11:23:15 [CPU] photo 1: 40000 points
2017-05-24 11:23:30 [CPU] photo 2: 40000 points
2017-05-24 11:23:43 [CPU] photo 3: 40000 points
2017-05-24 11:23:58 [CPU] photo 4: 40000 points
2017-05-24 11:24:11 [CPU] photo 5: 40000 points
2017-05-24 11:24:27 [CPU] photo 6: 40000 points
2017-05-24 11:24:42 [CPU] photo 7: 40000 points
2017-05-24 11:24:57 [CPU] photo 8: 40000 points
2017-05-24 11:25:11 [CPU] photo 9: 40000 points
2017-05-24 11:25:11 points detected in 168.078 sec
2017-05-24 11:25:11 Matching points...
2017-05-24 11:25:44 29922 matches found in 33.316 sec
2017-05-24 11:25:44 matches combined in 0.006 sec
2017-05-24 11:25:44 matches filtered in 0.145 sec
2017-05-24 11:25:44 finished matching in 201.661 sec
2017-05-24 11:25:44 setting point indices... 10173 done in 0.003 sec
2017-05-24 11:25:44 generated 10173 tie points, 2.25351 average projections
2017-05-24 11:25:44 removed 26 multiple indices
2017-05-24 11:25:44 removed 6 tracks
2017-05-24 11:25:44 selected 10167 tracks out of 10167 in 0.002 sec
2017-05-24 11:25:44 Estimating camera locations...
2017-05-24 11:25:44 processing block: 10 photos
2017-05-24 11:25:45 pair 4 and 5: 1852 robust from 1852
2017-05-24 11:25:45 adding photos 4 and 5 (1852 robust)
2017-05-24 11:25:45 adding 1852 points, 0 far (20.316 threshold), 0 inaccurate, 0 invisible, 0 weak
2017-05-24 11:25:45 adjusting: xx 0.220504 -> 0.218513
2017-05-24 11:25:45 adding 0 points, 0 far (20.316 threshold), 0 inaccurate, 0 invisible, 0 weak
2017-05-24 11:25:45 optimized in 0.041 seconds
2017-05-24 11:25:45 adding camera 6 (3 of 10), 502 of 502 used
2017-05-24 11:25:45 adding camera 3 (4 of 10), 465 of 465 used
2017-05-24 11:25:45 adding 2317 points, 0 far (20.316 threshold), 0 inaccurate, 0 invisible, 0 weak
2017-05-24 11:25:45 adjusting: xxx 0.575126 -> 0.334785
2017-05-24 11:25:45 adding 0 points, 0 far (20.316 threshold), 0 inaccurate, 0 invisible, 0 weak
2017-05-24 11:25:45 optimized in 0.055 seconds
2017-05-24 11:25:45 adding camera 2 (5 of 10), 510 of 510 used
2017-05-24 11:25:45 adding 1429 points, 0 far (20.316 threshold), 0 inaccurate, 0 invisible, 0 weak
2017-05-24 11:25:45 adjusting: xxx 0.367498 -> 0.32021
2017-05-24 11:25:45 adding 0 points, 0 far (20.316 threshold), 0 inaccurate, 0 invisible, 0 weak
2017-05-24 11:25:45 optimized in 0.096 seconds
2017-05-24 11:25:45 adding camera 1 (6 of 10), 460 of 460 used
2017-05-24 11:25:45 adding 1024 points, 0 far (20.316 threshold), 0 inaccurate, 0 invisible, 0 weak
2017-05-24 11:25:45 adjusting: xxx 0.382352 -> 0.359649
2017-05-24 11:25:45 adding 0 points, 0 far (20.316 threshold), 0 inaccurate, 0 invisible, 0 weak
2017-05-24 11:25:45 optimized in 0.104 seconds
2017-05-24 11:25:45 adding camera 7 (7 of 10), 214 of 214 used
2017-05-24 11:25:45 adding 901 points, 0 far (20.316 threshold), 0 inaccurate, 0 invisible, 0 weak
2017-05-24 11:25:45 adjusting: xxx 0.36835 -> 0.352613
2017-05-24 11:25:45 adding 0 points, 0 far (20.316 threshold), 0 inaccurate, 0 invisible, 0 weak
2017-05-24 11:25:45 optimized in 0.098 seconds
2017-05-24 11:25:45 adding camera 8 (8 of 10), 245 of 248 used
2017-05-24 11:25:45 adding 927 points, 3 far (20.316 threshold), 0 inaccurate, 1 invisible, 0 weak
2017-05-24 11:25:45 adjusting: xxxxxxxxxx 0.369721 -> 0.365791
2017-05-24 11:25:45 adding 1 points, 0 far (20.316 threshold), 0 inaccurate, 1 invisible, 0 weak
2017-05-24 11:25:45 optimized in 0.404 seconds
2017-05-24 11:25:45 adding camera 9 (9 of 10), 133 of 133 used
2017-05-24 11:25:45 adding 1022 points, 0 far (20.316 threshold), 0 inaccurate, 1 invisible, 0 weak
2017-05-24 11:25:45 adjusting: xxxxxxxxxx 0.502689 -> 0.345043
2017-05-24 11:25:46 adding 1 points, 0 far (20.316 threshold), 0 inaccurate, 1 invisible, 0 weak
2017-05-24 11:25:46 optimized in 0.482 seconds
2017-05-24 11:25:46 adding camera 0 (10 of 10), 8 of 9 used
2017-05-24 11:25:46 adding 681 points, 1 far (20.316 threshold), 0 inaccurate, 1 invisible, 0 weak
2017-05-24 11:25:46 adjusting: xxxxxxxxxx 0.464326 -> 0.386769
2017-05-24 11:25:46 adding 1 points, 0 far (20.316 threshold), 0 inaccurate, 1 invisible, 0 weak
2017-05-24 11:25:46 optimized in 0.477 seconds
2017-05-24 11:25:46 3 sigma filtering...
2017-05-24 11:25:46 adjusting: xxxxxx 0.386135 -> 0.254723
2017-05-24 11:25:47 point variance: 0.208083 threshold: 0.624248
2017-05-24 11:25:47 adding 0 points, 58 far (0.624248 threshold), 0 inaccurate, 0 invisible, 0 weak
2017-05-24 11:25:47 adjusting: xxxxxxxx 0.121902 -> 0.121103
2017-05-24 11:25:47 point variance: 0.0988846 threshold: 0.296654
2017-05-24 11:25:47 adding 0 points, 260 far (0.296654 threshold), 0 inaccurate, 0 invisible, 0 weak
2017-05-24 11:25:47 adjusting: xxx 0.100413 -> 0.100315
2017-05-24 11:25:47 point variance: 0.0817624 threshold: 0.245287
2017-05-24 11:25:47 adding 22 points, 209 far (0.245287 threshold), 0 inaccurate, 0 invisible, 0 weak
2017-05-24 11:25:47 adjusting: xxx 0.0926575 -> 0.0925865
2017-05-24 11:25:47 point variance: 0.07537 threshold: 0.22611
2017-05-24 11:25:47 adding 63 points, 148 far (0.22611 threshold), 0 inaccurate, 0 invisible, 0 weak
2017-05-24 11:25:47 adjusting: xx 0.0897645 -> 0.089738
2017-05-24 11:25:47 point variance: 0.0729803 threshold: 0.218941
2017-05-24 11:25:47 adding 90 points, 141 far (0.218941 threshold), 0 inaccurate, 0 invisible, 0 weak
2017-05-24 11:25:47 optimized in 0.974 seconds
2017-05-24 11:25:47 f 10869.6, cx 0, cy 0, k1 -0.0375387, k2 0.0257031, k3 0
2017-05-24 11:25:47 finished sfm in 2.975 seconds
2017-05-24 11:25:47 coordinates applied in 0 sec
2017-05-24 11:25:48 Finished processing in 204.72 sec (exit code 1)

84

General / Re: Align Cameras for Aerial Imagery - 5 hours for 200 images with 750GB memory?

« on: May 24, 2017, 06:10:30 PM »

The images are compressed jpg, ~15MB in size. Exiftool gives me the following information:
Dimensions: 11608 x 8708
Resolution: 300dpi
Bit depth: 24

Camera information:
Make: Phase One
Model: iXU1000-R
F-stop: f/5
Exposure: 1/1600 sec
ISO speed: 200
Focal length: 50mm

PhotoScan 1.3.2 is also reading this:
Sensor X res: 217.391
Sensor Y res: 217.391

although exiftdata says
Focal Plane X Resolution        : 2173.913055
Focal Plane Y Resolution        : 2173.913055

not sure if that difference matters.


I'll try to run it again on my 64-bit Windows 7 machine and see how the speed is. The stats on this machine:
Processor: Intel Core i7-6600U CPU @ 2.60GHz 2.80 GHz
Installed memory (RAM): 16.0 GB (15.7GB usable)


I have the demo version of 1.3.2 installed on this machine.

85

General / Re: Align Cameras for Aerial Imagery - 5 hours for 200 images with 750GB memory?

« on: May 24, 2017, 04:14:05 PM »

Attached is the log from starting the program and aligning cameras for one chunk. 5 hours total. Nothing stands out too much, just takes about 1-2 minutes for each photo and that brings it all up to 5 hours.

Excerpt:

2017-05-23 19:55:52 photo 1: 39936 points
2017-05-23 19:56:39 photo 2: 39925 points
2017-05-23 19:57:18 photo 3: 39936 points
2017-05-23 19:57:47 photo 4: 39934 points
2017-05-23 19:58:29 photo 5: 39936 points
2017-05-23 19:59:04 photo 6: 39936 points
2017-05-23 19:59:43 photo 7: 39930 points
2017-05-23 20:00:25 photo 8: 39936 points
2017-05-23 20:01:05 photo 9: 39936 points
2017-05-23 20:01:41 photo 10: 39936 points
2017-05-23 20:02:17 photo 11: 39936 points
2017-05-23 20:03:02 photo 12: 39936 points

86

General / Re: Align Cameras for Aerial Imagery - 5 hours for 200 images with 750GB memory?

« on: May 24, 2017, 05:36:51 AM »

Hm. I tried again with that command and it still says it expects to take 4 hours for 200 pictures.
This is with 40k/4k for the limits and reference preselection.

I ran "htop" on my command line which now shows all 72 cpus at close to 100%, and about 14G/750G memory being used.

Does this seem like the right amount of time it should be taking? My images are all in a line (every 3 seconds)., but they are a LOT of tree canopies, so I don't know if the difficulty of the matching makes an impact. A few times when I ran this I only got 120/200 cameras aligned, so I'm assuming it's having some difficulty with the extremely green photos.

I'll post the log when it finishes.

87

General / Re: Align Cameras for Aerial Imagery - 5 hours for 200 images with 750GB memory?

« on: May 24, 2017, 02:53:47 AM »

Ooook, I finally get it. You meant to type it in this order:

"numactl --interleave=all /my/path/to/photoscan.sh" 

I'll see how it goes. THanks.

88

General / Re: Align Cameras for Aerial Imagery - 5 hours for 200 images with 750GB memory?

« on: May 24, 2017, 02:51:41 AM »

--

89

General / Re: Align Cameras for Aerial Imagery - 5 hours for 200 images with 750GB memory?

« on: May 24, 2017, 02:46:38 AM »

--

90

General / Re: Align Cameras for Aerial Imagery - 5 hours for 200 images with 750GB memory?

« on: May 23, 2017, 10:02:36 PM »

I ran this command for some information on cpu: "lscpu"

Architecture:          x86_64
CPU op-mode(s):        32-bit, 64-bit
Byte Order:            Little Endian
CPU(s):                72
On-line CPU(s) list:   0-71
Thread(s) per core:    2
Core(s) per socket:    18
Socket(s):             2
NUMA node(s):          2
Vendor ID:             GenuineIntel
CPU family:            6
Model:                 79
Model name:            Intel(R) Xeon(R) CPU E5-2695 v4 @ 2.10GHz
Stepping:              1
CPU MHz:               2599.980
BogoMIPS:              4204.74
Virtualization:        VT-x
L1d cache:             32K
L1i cache:             32K
L2 cache:              256K
L3 cache:              46080K
NUMA node0 CPU(s):     0,2,4,6,8,10,12,14,16,18,20,22,24,26,28,30,32,34,36,38,40,42,44,46,48,50,52,54,56,58,60,62,64,66,68,70
NUMA node1 CPU(s):     1,3,5,7,9,11,13,15,17,19,21,23,25,27,29,31,33,35,37,39,41,43,45,47,49,51,53,55,57,59,61,63,65,67,69,71

For gpu, I check using "lspci -v -s $(lspci | grep VGA | cut -d" " -f 1)":

0a:00.0 VGA compatible controller: Matrox Electronics Systems Ltd. G200eR2 (rev 01) (prog-if 00 [VGA controller])
        Subsystem: Dell Device 0627
        Flags: bus master, medium devsel, latency 64, IRQ 19, NUMA node 0
        Memory at 90000000 (32-bit, prefetchable) [size=16M]
        Memory at 91800000 (32-bit, non-prefetchable) [size=16K]
        Memory at 91000000 (32-bit, non-prefetchable) [size=8M]
        Expansion ROM at <unassigned> [disabled]
        Capabilities: <access denied>
        Kernel driver in use: mgag200
        Kernel modules: mgag200


I don't have a log available right now as it is running and says 3 more hours til it will be complete. I could abort it and try again with only 10 pictures and provide the log for that in < 30 minutes?