Messages

31

Bug Reports / Re: Time estimates for network jobs not correct

« on: June 03, 2017, 04:37:40 PM »

I see. Thanks. So I guess there's no way to know how long it really took from the show Info?

32

Bug Reports / Time estimates for network jobs not correct

« on: May 31, 2017, 06:33:32 PM »

I've been noticing that when I run a job on our network and then look at the Show Info dialog for the Chunk, the times for each step are wrong, in some cases very wrong.  For instance I just ran a batch process which I know took 4-5 hours to finish.  I can confirm this by looking at the details option for the job in the network monitor.  Here it says the Dense stage in total took a bit over 3 hours.  However the Show Info dialog says depth map generation took 2 hours and 21 min and dense cloud generation took 11 hours and 44 min.  The alignment numbers are also too large. Any idea what's going on here?

33

General / Re: Calculating volume and surface area of a mesh

« on: April 23, 2017, 03:08:20 PM »

I've recently upgraded to version 1.3.1 and I notice the calculated area is now rounded to the nearest m2.  It used to have two decimal places.  Is there somewhere to increase the significant digits reported?

34

General / Re: Performance 1.2.5 vs 1.3.0 and gpu usage

« on: April 21, 2017, 05:09:51 PM »

I'm also experiencing much slower Dense cloud build times lately and in retrospect I think it started since updating to 1.3 and now 1.3.1. We run a network of four machines. For projects of 1000 photos it would take 2-4 hours to build the cloud on medium quality and moderate depth filtering. I've been running much smaller projects 400-500 photos with the same settings and it's taking sometimes 8-9 hours. We upgraded to 1.3.1 a few days ago and I think it's possibly a bit worse. I'm just responding here as I'm wondering if anybody else is experiencing similar issues.

35

General / Estimating surface area for subsets of multiple aligned models

« on: September 10, 2015, 01:40:57 AM »

I've an application where I want to compare the surface area of the mesh from multiple models created independently of the same scene. But I'd like to do this for multiple sub-regions within the bounds of the models. The scene is about 5 x 12 meters and ideally I'd like to just grid this up into 1m x 1m boxes, get the surface area within each box for each independent model, and then I can compare them.  I've aligned the meshes from each scene. I don't think there is a way to overlay a grid like I've described but I'm wondering if there are options to get this information by iterating over all triangles in the mesh and summing areas into spatial bins based on the spatial position within the mesh (from coordinates of the vertices).  I have some experience with Python scripting, can this be done that way from within photoscan? Or is there a way to export the data on the vertices (x,y,z positions for each one) in a text format I can read into another scripting environment (VB, Matlab...) to do the summary? Thanks for your help.