46
General / Re: Process four band images
« on: November 30, 2018, 03:22:17 PM »
No answers from me, but I'd be really interested in the results.
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.
47
General / Re: Exporting large orthomosaics
« on: November 30, 2018, 03:21:11 PM »
Consider using the "split into blocks" option in the export window. This will split the final ortho into a grid of more managable sized tiles.
This may not work with your workflow, but it would certainly help with the direct problem you describe. It may also be workable to output these for preview purposes and then export a single huge file for the finished result.
This may not work with your workflow, but it would certainly help with the direct problem you describe. It may also be workable to output these for preview purposes and then export a single huge file for the finished result.
48
General / Re: Installing and running Agisoft on a Linux HPC cluster
« on: November 29, 2018, 02:48:18 PM »
A node (that is a single computer which has a single operating system installed on it) requires one licence, regardless of how many cores the processor has.
multiple nodes across a network can be set up for advanced configurations, where each processing node and each client machine needs a licence. If I machine is being used both as a client machien and a processing node, I understand it only needs a single licence. (there is also a need for a server on the network to coordinate the nodes, but it does not need a licence)
Note that floating licences are more expensive than node locked licences, but node locked licences can still be transfered between computers by deactivating the licences on the first, and typign the licence code into the second.
multiple nodes across a network can be set up for advanced configurations, where each processing node and each client machine needs a licence. If I machine is being used both as a client machien and a processing node, I understand it only needs a single licence. (there is also a need for a server on the network to coordinate the nodes, but it does not need a licence)
Note that floating licences are more expensive than node locked licences, but node locked licences can still be transfered between computers by deactivating the licences on the first, and typign the licence code into the second.
49
General / Graphics card options
« on: November 29, 2018, 02:09:00 PM »
In a high end graphics workstation, being built specifcally for photoscan (64GB ram, 9920x), I'm trying to work out which graphics card to include. My workload is likelly to be objects (rather than landscapes) and there will be image sets well into the high hundres of images processed sometimes -- I intend to push the capabilities of the the machine as far as I can.
Options (within budget) are:
GTX 1080 ti -- has 11GB of memory, this is the current default.
RTX 2080 -- similarish performance to above, lower cuda core count, and lower memory.
2x GTX 1070 -- still within budget (just), worse upgrade options as we only really have space for 2 cards.
My question is -- for raw processing speed on large data sets, which of these options will give the best performace?
Secondary questions: is the 11GB of memory in the 1080 ti a significant benifit to the process? I have a theory, that I'm unable to test, that larger datasets (which none of the benchmarks cover perticularly well) will benifit from this, where the smaller datasets won't.
We know from Pugit System's testing that a second graphics card gives a 20% - 25% boost to performance under thier test conditions, how is this likelly to manifest in my situation?
Options (within budget) are:
GTX 1080 ti -- has 11GB of memory, this is the current default.
RTX 2080 -- similarish performance to above, lower cuda core count, and lower memory.
2x GTX 1070 -- still within budget (just), worse upgrade options as we only really have space for 2 cards.
My question is -- for raw processing speed on large data sets, which of these options will give the best performace?
Secondary questions: is the 11GB of memory in the 1080 ti a significant benifit to the process? I have a theory, that I'm unable to test, that larger datasets (which none of the benchmarks cover perticularly well) will benifit from this, where the smaller datasets won't.
We know from Pugit System's testing that a second graphics card gives a 20% - 25% boost to performance under thier test conditions, how is this likelly to manifest in my situation?
50
General / Photoscan per user settings
« on: November 07, 2018, 10:44:40 PM »
Hi,
I'm on a university campus where each user has thier own login details to the windows domain. I have discovered to my dismay that most of (all of?) the settings in photoscan are per user settings.
Few of these settings are important, but one of them is the tickbox that tells it to use the GPU for processing, this means that for months every user except me has been running with no GPU assistance.
I may be rolling out network processing soon, and I expect there will be many settings that are important for that.
Is there a way to fix this for all users?
Thanks,
JRP
I'm on a university campus where each user has thier own login details to the windows domain. I have discovered to my dismay that most of (all of?) the settings in photoscan are per user settings.
Few of these settings are important, but one of them is the tickbox that tells it to use the GPU for processing, this means that for months every user except me has been running with no GPU assistance.
I may be rolling out network processing soon, and I expect there will be many settings that are important for that.
Is there a way to fix this for all users?
Thanks,
JRP
51
General / Re: Network cluster setup questions
« on: November 07, 2018, 10:40:11 PM »Quote1)Can I run 2 workstations as both a processing nodes and a client nodes? To do this, do I need to run photoscan twice on each workstation (once from commandline with –node; and once from gui), or is there a way to configure photoscan to act as both node and client?
Yes, but I can't imagine why you would. Unless you want to have the ability to use the workstation as a node during off hours. Depending on what task the node is doing, it can be difficult to check email or watch videos while Photoscan is working.
Thank you very much SB for your detailed response, it helped lots.
It is a university lab, we will occasionally have big jobs that need lots of resource, and ocasionally have people working separatly on student projects. This way we can disconnect the machines as nodes, send data to be processed, then reconnect them both and let it run. The aim is adaptability.
I understood (from the manual) that the job manager doesn't need a licence, do you know diferent?Quote3)If running it as above, do I need 4 licences, or will the 2 licences I have be good enough?two for the workstations and one for the job manager, so 3 licenses
This is a question about usability, and how the indevidual connects and disconnects from the network processing infrastructure. Information on how easy the interface is to use is hard to come by.Quote6)We have a staff member with a laptop with photoscan on, can they easily connect up to the network and run as a client, then easily switch to standalone for field use?
If you have a static license (node-locked) license there is nothing to do. I think a roaming license would require you to do a license checkout before leaving the network.
52
General / Floating licence server on linux?
« on: October 25, 2018, 01:55:38 PM »
Is it possible ot run a floating licence server on linux?
Manual sugests that the server executable is a .exe file, which sugests it may be winodws only.
We don't have any windows servers available, and my organisiation has a system for providing licence broker servers as VMs (which is specifically excluded I understand), so no good options there.
It would be unforutnate to have to provision an entire hardware server to run 24/7 just to host a single licence server when we already have good linux servers running.
Manual sugests that the server executable is a .exe file, which sugests it may be winodws only.
We don't have any windows servers available, and my organisiation has a system for providing licence broker servers as VMs (which is specifically excluded I understand), so no good options there.
It would be unforutnate to have to provision an entire hardware server to run 24/7 just to host a single licence server when we already have good linux servers running.
53
General / Network cluster setup questions
« on: October 18, 2018, 02:00:04 PM »
I have 2 (moderately) powerful windows workstations and 2 headless Linux servers, I would like to set up a network cluster. There are some details not clear in the documentation though. Sorry for the long list of questions:
1)Can I run 2 workstations as both a processing nodes and a client nodes? To do this, do I need to run photoscan twice on each workstation (once from commandline with –node; and once from gui), or is there a way to configure photoscan to act as both node and client?
2)Computers on our site use windows domain logins, I notice many settings (including turning on GPU processing!) are stored as a per user setting, is there a simple way to configure things so that user training is minimal in how to add network processing on the workstations?
3)If running it as above, do I need 4 licences, or will the 2 licences I have be good enough?
4)I may consider buying more licences and running the 2 headless Linux boxes also as nodes (they are dual Xeon E5-2640 v3 with no graphics cards – so not ideal, but not slow either) – is running the server and a node on the same machine a problem?
5)Are there any reliability issues with running a mixed Linux windows environment? (other than the simple to fix --root file path stuff?)
6)We have a staff member with a laptop with photoscan on, can they easily connect up to the network and run as a client, then easily switch to standalone for field use?
7)Also, how much network traffic is there with the network processing? Would the system benefit from 10Gbit ethernet, or is gigabit good enough? How much does latency on the network file store affect performance? Do the nodes cache data locally? Would they benefit from SSDs?
1)Can I run 2 workstations as both a processing nodes and a client nodes? To do this, do I need to run photoscan twice on each workstation (once from commandline with –node; and once from gui), or is there a way to configure photoscan to act as both node and client?
2)Computers on our site use windows domain logins, I notice many settings (including turning on GPU processing!) are stored as a per user setting, is there a simple way to configure things so that user training is minimal in how to add network processing on the workstations?
3)If running it as above, do I need 4 licences, or will the 2 licences I have be good enough?
4)I may consider buying more licences and running the 2 headless Linux boxes also as nodes (they are dual Xeon E5-2640 v3 with no graphics cards – so not ideal, but not slow either) – is running the server and a node on the same machine a problem?
5)Are there any reliability issues with running a mixed Linux windows environment? (other than the simple to fix --root file path stuff?)
6)We have a staff member with a laptop with photoscan on, can they easily connect up to the network and run as a client, then easily switch to standalone for field use?
7)Also, how much network traffic is there with the network processing? Would the system benefit from 10Gbit ethernet, or is gigabit good enough? How much does latency on the network file store affect performance? Do the nodes cache data locally? Would they benefit from SSDs?
54
General / Re: Camera based chunk alignment - how does this work
« on: August 03, 2018, 12:04:38 PM »
Ah! Now it's starting to make sense, I'd forgotten about that use case.
55
General / Re: Camera based chunk alignment - how does this work
« on: August 02, 2018, 04:25:06 PM »
Ok, that's great.
Do you end up in a situation where you have duplicate phtots when you combine the chunks? or does it handle this in some other way?
Do you end up in a situation where you have duplicate phtots when you combine the chunks? or does it handle this in some other way?
56
General / Camera based chunk alignment - how does this work
« on: August 01, 2018, 07:25:23 PM »
Hi,
I have been given a very large dataset to process, with only a very small number of GCPs (only one of my chunks has more than 1) and I need to somehow align the chunks.
I've just spent half a day visually searching for common points in more than one chunk, this doesn't seem to have helped with anything
Camera based alignment sounds like a great idea from the name, but I cannot find any documentation about how it works, or what I need to do to to get it to work. other than in the manual it says "Camera based
method is used to align chunks based on estimated camera locations. Corresponding cameras should
have the same label."
Presumably the same image file needs to be loaded into more than one chunk, and presumably "label" means file name?
Could really do with a decent youtube video of someone demoing this about now.
I have been given a very large dataset to process, with only a very small number of GCPs (only one of my chunks has more than 1) and I need to somehow align the chunks.
I've just spent half a day visually searching for common points in more than one chunk, this doesn't seem to have helped with anything
Camera based alignment sounds like a great idea from the name, but I cannot find any documentation about how it works, or what I need to do to to get it to work. other than in the manual it says "Camera based
method is used to align chunks based on estimated camera locations. Corresponding cameras should
have the same label."
Presumably the same image file needs to be loaded into more than one chunk, and presumably "label" means file name?
Could really do with a decent youtube video of someone demoing this about now.
57
General / Sequence for combining Chunks
« on: May 18, 2016, 12:05:15 AM »
I am new to using Chunks.
I am processing details of architecture on the ceiling of a cathedral.
I have 2 chunks, one of a wider area including the walls of the room, and some ground control points, I added the images and ran camera alignment, added the GCPs then ran camera alignment, the results looked good.
I then added a second chunk, of a small area of the ceiling, aligned cameras, results for this chunk look good though not correctly oriented.
My intention is that the first chunk is only used to provide scale and orientation for the second.
When I align the chunks, the GCP errors become huge and the model ends up rotated wildly, losing all the effort of setting up the GCPs.
What am I doing wrong?
I am processing details of architecture on the ceiling of a cathedral.
I have 2 chunks, one of a wider area including the walls of the room, and some ground control points, I added the images and ran camera alignment, added the GCPs then ran camera alignment, the results looked good.
I then added a second chunk, of a small area of the ceiling, aligned cameras, results for this chunk look good though not correctly oriented.
My intention is that the first chunk is only used to provide scale and orientation for the second.
When I align the chunks, the GCP errors become huge and the model ends up rotated wildly, losing all the effort of setting up the GCPs.
What am I doing wrong?
58
General / Re: Should we use Lens Profile Correction in Photoshop before importing into PScan?
« on: January 01, 2016, 04:15:29 PM »
I have a similar question: I have a sony a77ii and a sony 16-50 f2.8ssm (24-75ish equivalent). it's a wonderful lens, but rather high distortion. I have had results come out looking distorted as a result.
Is it preferable to use adobe corrections to go part of the way, then let PS finish the job, or is it best to give the fresh files to PS to work on all the way through?
Is there a procedure that can allow me to generate a lens profile in PS that I can reuse in future?
Is it preferable to use adobe corrections to go part of the way, then let PS finish the job, or is it best to give the fresh files to PS to work on all the way through?
Is there a procedure that can allow me to generate a lens profile in PS that I can reuse in future?
59
General / Re: Bounding box rotation.
« on: December 29, 2015, 01:16:08 PM »
Excellent, that's very useful.
The other part of the question remains unanswered though: what does this bounding box actually do though, if it is at an angle, does it actually affect anything other than determining which areas get processed?
How is it generated in the first place? it must have been a lot of work to create it in such a way that it isn't parallel to the local coordinates.
The other part of the question remains unanswered though: what does this bounding box actually do though, if it is at an angle, does it actually affect anything other than determining which areas get processed?
How is it generated in the first place? it must have been a lot of work to create it in such a way that it isn't parallel to the local coordinates.
60
General / Re: Getting vertical right
« on: December 29, 2015, 01:06:33 PM »
There are certainly some good ideas there.
A ranging pole with a bubble level would provide a good equivalent to the plumb bob option, I'm not sure it would be as accurate, but it may be ideal for some people.
@Kiesel: I have looked at laser levels before, but I could not work out how to set one up in a way that would be useful; photoscan is very specific and limited over what it will accept.
A ranging pole with a bubble level would provide a good equivalent to the plumb bob option, I'm not sure it would be as accurate, but it may be ideal for some people.
@Kiesel: I have looked at laser levels before, but I could not work out how to set one up in a way that would be useful; photoscan is very specific and limited over what it will accept.
