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

Pages: 1 [2] 3
16
General / Re: Agisoft PhotoScan 1.4.0 pre-release
« on: November 01, 2017, 07:58:14 PM »
Please have a look at the log.
I processed a project till the DOM stage.
But when I try to export the DEM, it finishes within 1 second and nothing has been output.
If I create DSM using sparse cloud it can output, but when I used dense cloud to generate the DSM, it cannot output.
It cannot output even when I selected to cut the output into 10000x10000 size tiles.

17
General / Re: Agisoft PhotoScan 1.4.0 pre-release
« on: November 01, 2017, 07:53:48 PM »
I got problem in exporting using latest build.

18
General / Re: Agisoft PhotoScan 1.4.0 pre-release
« on: November 01, 2017, 08:12:41 AM »
Can I know what is this problem?
Build 5251

19
General / Re: Agisoft PhotoScan 1.4.0 pre-release
« on: October 29, 2017, 10:20:56 PM »
Hello rexsham,

On your screenshot (see cropped image below) there are two node instances connected to the server, both nodes are running version 5097, server is running 5251. Both instances are run on host 192.168.1.166. While the server is run on 192.168.1.161 and from the same host (.161) you are trying to start updated node.

So if any other node is trying to connect and doesn't have proper version installed (exactly the same as already connected nodes), you'll get version mismatch issue.

Thank you very much Alexey.
After your explanation I finally understand that "Version mismatch" does not mean the Node and Server version mismatch, it actually means that more than 1 node that are running different versions of node is connected to server at the same time.

I would kindly suggest that changing the "Version Mismatch" into "Nodes running different versions are not allowed, please make sure all the nodes are running the same Version and Build of Photoscan."
The original message "Version Mismatch" is a bit confusing and I think that means it is a server and node version mismatch.

Anyway thank you so much! 1.4 has a lot of great improvements. Make sure the new features are well documented in the user guide and your website tutorials. The tutorials on the web are severely outdated.

20
General / Re: Agisoft PhotoScan 1.4.0 pre-release
« on: October 27, 2017, 03:33:00 PM »
Hello rexsham,

Can you check with the Network Monitor if there are any other nodes (that are on version 5097) that are connected to your server?

There are no other nodes that are on version 5097 in the network.

In the image that I attached in the previous post is running the Network Monitor. There are only two computers in the network, one running 5097 as the node, one running 5251 as the server. You can see the 192.168.1.166 has been connected to the 5097 server. And the node running on 192.168.1.161 (the server that is running 5251 itself cannot connect to itself)

21
General / Re: Agisoft PhotoScan 1.4.0 pre-release
« on: October 27, 2017, 11:58:07 AM »
Hello rexsham,

Version mismatch means is related to the nodes version. Only same version nodes may connect to the same server.

Let me rearrange my statement again.

I am using a 5251 build node to connect to 5251 build server in the SAME computer.
It does not work. It shows Version mismatch.

BUT, I can connect a 5097 node (which is another computer on the network) to a 5251 server, this is strange.

Have a closer look at the image attached.
This is the computer with IP 192.168.1.161
192.168.1.161 is the computer running server 5251 build
192.168.1.166 is the computer on network running node 5097 (IT CAN REGISTER, which it should not)
When I try to invoke a node with 5251 build on 192.168.1.161 on the same computer, it failed.





22
Version Mismatch in Network Mode
I installed 1.4.0  5251

But if I use Build 5251 node to connect to the same computer's server , it will show version mismatch.

At the same time, the computer that is running "Server" will accept "nodes" that are running Build 5097.

i.e.
This is a bug that Build 5251 Server accepts nodes running Build 5097 only but not accept nodes running 5251.


23
General / AMD Vega64 vs Nvidia GTX 1080 vs GTX 1080Ti
« on: October 10, 2017, 12:55:19 PM »
Can anyone or Agisoft tell, which card is faster when running Photoscan?

Assume all other factors constant.
We are building a new machine and speed is the key, don't care about the cost first.

24
Bug Reports / PS1.3 Build 3520 Error: out of memory at line 177
« on: March 05, 2017, 02:34:27 PM »
I have installed latest driver of R9 390X and GTX780
When I run Align Photos with a 500 images dataset, I get this error.
I can process if I uncheck all GPU options.
I have tried reinstalling PS1.3 , nvidia and amd drivers, problem persists.


2017-03-05 19:26:53 Agisoft PhotoScan Professional Version: 1.3.0 build 3520 (64 bit)
2017-03-05 19:26:53 Platform: Windows
2017-03-05 19:26:54 OpenGL Vendor: ATI Technologies Inc.
2017-03-05 19:26:54 OpenGL Renderer: AMD Radeon (TM) R9 390 Series
2017-03-05 19:26:54 OpenGL Version: 4.5.13469 Compatibility Profile Context 21.19.519.2
2017-03-05 19:26:54 Maximum Texture Size: 16384
2017-03-05 19:26:54 Quad Buffered Stereo: not enabled
2017-03-05 19:26:54 ARB_vertex_buffer_object: supported
2017-03-05 19:26:54 ARB_texture_non_power_of_two: supported
2017-03-05 19:27:00 LoadProject
2017-03-05 19:27:00 Loading project...
2017-03-05 19:27:13 loaded project in 12.674 sec
2017-03-05 19:27:13 Finished processing in 12.675 sec (exit code 1)
2017-03-05 19:27:36 AlignPhotos: accuracy = Highest, preselection = generic, reference, keypoint limit = 40000, tiepoint limit = 4000, adaptive fitting = 1
2017-03-05 19:27:36 Detecting points...
2017-03-05 19:27:36 Using device: GeForce GTX 780, 12 compute units, 3072 MB global memory, CUDA 3.5
2017-03-05 19:27:36   max work group size 1024
2017-03-05 19:27:36   max work item sizes [1024, 1024, 64]
2017-03-05 19:27:36 Using device: Hawaii, 44 compute units, 8192 MB global memory, OpenCL 2.0
2017-03-05 19:27:36   max work group size 256
2017-03-05 19:27:36   max work item sizes [256, 256, 256]
2017-03-05 19:27:36   max mem alloc size 4048 MB
2017-03-05 19:27:36   wavefront width 64
2017-03-05 19:27:40 Device 1
2017-03-05 19:27:40    Program build log:
2017-03-05 19:27:40 Error: Undeclared function index 1025
2017-03-05 19:27:40
2017-03-05 19:27:40
2017-03-05 19:27:40 Finished processing in 4.368 sec (exit code 0)
2017-03-05 19:27:40 Error: out of memory at line 177
2017-03-05 19:28:16 DuplicateChunk: items = ()
2017-03-05 19:28:16 Duplicating chunk...
2017-03-05 19:28:18 Finished processing in 1.2 sec (exit code 1)
2017-03-05 19:29:24 AlignPhotos: accuracy = Highest, preselection = generic, reference, keypoint limit = 40000, tiepoint limit = 4000, adaptive fitting = 1
2017-03-05 19:29:24 Detecting points...
2017-03-05 19:29:24 Using device: GeForce GTX 780, 12 compute units, 3072 MB global memory, CUDA 3.5
2017-03-05 19:29:24   max work group size 1024
2017-03-05 19:29:24   max work item sizes [1024, 1024, 64]
2017-03-05 19:29:24 Using device: Hawaii, 44 compute units, 8192 MB global memory, OpenCL 2.0
2017-03-05 19:29:24   max work group size 256
2017-03-05 19:29:24   max work item sizes [256, 256, 256]
2017-03-05 19:29:24   max mem alloc size 4048 MB
2017-03-05 19:29:24   wavefront width 64
2017-03-05 19:29:28 Device 1
2017-03-05 19:29:28    Program build log:
2017-03-05 19:29:28 Error: Undeclared function index 1025
2017-03-05 19:29:28
2017-03-05 19:29:28
2017-03-05 19:29:28 Finished processing in 3.829 sec (exit code 0)
2017-03-05 19:29:28 Error: out of memory at line 177

25
Thank you very much bigben!

26
I know PScan can undistort photos automatically using the detected feature points during the Align Photos step.
But what I am confuse is that if our camera has a built in lens profile in Adobe Lightroom, like Sony DSC-RX1, when we export the photos after exposure adjustments, should we also apply the lens correction profile to undistort the photos before importing the JPGs into PScan?
Will this affect the accuracy of the output of DEM and DOM? Better or Worse?

27
General / Re: Agisoft PhotoScan 1.2.0 pre-release
« on: December 04, 2015, 11:25:21 PM »
Using the Raster Calculator feature, by just clicking on the "B3- Blue" channel in the Raster Calculator
It immediately shows "Invaid Expression". But this error does not appear on B1-Red and B2-Green.
This should be a bug.

I understand that we should just input B1, B2 or B3 instead of "B3- Blue", but clicking the "B3- Blue" button automatically inputs "B3- Blue", which makes users confuse, it should just input B3 .

28
Thanks both,

My drivers are latest already and reboot resumes the normal operation of the program.

I just try it randomly with a large number.
I suggest there should be automatic abort or warning to stop users from getting their machines into weird status and need to force close the program.

I can finish the job with a 10000 x 10000 image without problem now.

29
I have a problem when using Photoscan Professional 1.0.4 build 1847
I am processing around 187 images with 5616*3744 resolution

From workspace I see this:
182cameras, 7 markers, 2797815points
Dense Cloud 142591765 points
3D Model 28370252 faces
Vertices 14192523

When I start to build Texture I selected:
Building Texture
Orthophoto
Mosaic
Texture size:
90000 x 1
Enable Colour Correction

I have a bounding box very tight
My computer has 32GB Ram, i5-2400 CPU and a Radeon 7850 with 2G Ram

What I got is Bad Allocation Error in the console.
The software did not prompt a dialog box but it just go into a "Not Responding" mode
While CPU usage is held around 60% and Ram usage is around 5G when it goes into "Not Responding" mode, also OpenCL shows GPU usage is around 60% too.

So I force closed the program. Now when I open the project again, the program becomes very slow and sometimes windows display "Program Not Responding" and it will recover after some random time and go into "Program Not Responding" again. The model view cannot be rotated anyway and when I drag the mouse, the program goes into  "Program Not Responding" and need to wait for a long time to recover.

The program consumes 60% of GPU and 70% of CPU and 6G Ram as long as the project loads and when I try to start building texture again, it will stay in Progress 0% forever.



30
Another way of asking the question is:
Will turning the focus ring affect the calibration results?

Pages: 1 [2] 3