46
General / Re: Agisoft PhotoScan 1.4.0 pre-release
« on: December 29, 2017, 11:48:51 PM »
Please see attached screen shot.
The Building Model stage is only using one core.
The Building Model stage is only using one core.
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: Agisoft PhotoScan 1.4.0 pre-release
« on: December 29, 2017, 11:39:12 PM »log file is too big.Maybe you can provide its final part that is related to the problematic operation only?
Without documentation of the console log how can i know what is the problematic operation?
Log file from the start of the process is 17Mb. so it's hard to see how to cut it down to 512kb
48
General / Re: Agisoft PhotoScan 1.4.0 pre-release
« on: December 29, 2017, 10:54:42 PM »
log file is too big.
49
General / Re: Agisoft PhotoScan 1.4.0 pre-release
« on: December 29, 2017, 09:14:06 PM »
I believe I'm experiencing some kind of stability problem with v1.4 Build 5532 Standard Edition.
The symptoms are that a very large number of Handles (16M and 31M on two separate runs) are created over time and my machine pretty much comes to a halt. By coming to a halt I mean unresponsive to mouse or keyboard.
Only one of the 36 available cores (core 2) is doing anything, it is at 100%. all other cores are essentially idle.
It's an Intel i9 with 128Gb memory and twin EVGA GTX 1080 Ti SC Gaming 11 GPUs.
This happens many hours (10+) into the photo alignment stage of processing a 7200+ camera model.
On one occasion while running the above mentioned big model I got impatient and started up a 2nd copy of Photoscan to build a mesh using the new algorithm on a model that I had originally aligned using version 1.3.4. It was a smaller model (3200 cameras). I noted during this run that again only core 2 was at 100%. It got to a stage with 16,000,000+ handles that neither copy of Photoscan seem to be making any progress. I tried pausing one then the other but neither paused or made any progress (no output to the console). When the copy of Photoscan that had been running for 12+ hours was killed the handles reduced to 15,000 or so proving it was the long running copy of Photoscan that appears to be leaking Handles.
PS: Memory usage is fairly low (<25% of 128GB).
HTH
The symptoms are that a very large number of Handles (16M and 31M on two separate runs) are created over time and my machine pretty much comes to a halt. By coming to a halt I mean unresponsive to mouse or keyboard.
Only one of the 36 available cores (core 2) is doing anything, it is at 100%. all other cores are essentially idle.
It's an Intel i9 with 128Gb memory and twin EVGA GTX 1080 Ti SC Gaming 11 GPUs.
This happens many hours (10+) into the photo alignment stage of processing a 7200+ camera model.
On one occasion while running the above mentioned big model I got impatient and started up a 2nd copy of Photoscan to build a mesh using the new algorithm on a model that I had originally aligned using version 1.3.4. It was a smaller model (3200 cameras). I noted during this run that again only core 2 was at 100%. It got to a stage with 16,000,000+ handles that neither copy of Photoscan seem to be making any progress. I tried pausing one then the other but neither paused or made any progress (no output to the console). When the copy of Photoscan that had been running for 12+ hours was killed the handles reduced to 15,000 or so proving it was the long running copy of Photoscan that appears to be leaking Handles.
PS: Memory usage is fairly low (<25% of 128GB).
HTH
50
Feature Requests / Auto Save
« on: December 24, 2017, 09:06:43 PM »
I'l like to see a feature where the project file gets automatically saved at the end of each processing stage.
51
Feature Requests / End of Processing notifcations
« on: December 24, 2017, 09:05:39 PM »
I'm thinking it might be handy to receive an email when each processing step ends. On long runs it would save having to check on progress.
52
Feature Requests / Console Message documentation
« on: December 24, 2017, 09:04:10 PM »
I'd be interested in a document that explains the messages that are output to the console
53
Feature Requests / Console Message documentation
« on: December 20, 2017, 11:37:34 PM »
Is there any documentation on the meaning of the messages that are logged to the Console window?
As i'm now spending a rather large proportion of my life watching these message scroll past it would be rather nice to understand what they actually means rather than what i think they mean.
As i'm now spending a rather large proportion of my life watching these message scroll past it would be rather nice to understand what they actually means rather than what i think they mean.
54
General / Support renewal
« on: November 17, 2017, 03:22:36 PM »
I note that the original purchase of a license included 1 year of email support and software updates (upto v1.9).
How much does 2nd and subsequent years costs for email support and software updates?
What is the reason for limiting updates to v1.9?
How much does 2nd and subsequent years costs for email support and software updates?
What is the reason for limiting updates to v1.9?
