Agisoft Metashape

Agisoft Metashape => General => Topic started by: MitchellT on January 14, 2019, 04:53:46 AM

Title: Depth Maps for newly aligned photos?
Post by: MitchellT on January 14, 2019, 04:53:46 AM
After I used markers to align about 12 photos with the 200 others aligned with depth maps in the Chunk., they now have check marks, but I have been unsuccessful in getting depth maps for these additional photos .

I am Using Metashape Pro, and have tried re-running sparse cloud tie points, building a dense cloud from the mixed photos etc.

I have deleted the markers, used to align the photos. Do I have to remove all the existing depth maps and start the tie point process from the beginning?

Thanks for any assistance.
Title: Re: Depth Maps for newly aligned photos?
Post by: Alexey Pasumansky on January 14, 2019, 11:30:59 AM
Hello MitchellT,

Metashape (as well as previously PhotoScan) is generating the depth maps for the overlapping pairs of images, considering the images to be overlapping basing on the number of valid tie points between them. If there number of tie points for the image pair is below the threshold, such pair would not be considered as overlapping and the depth maps wouldn't be generated for it.

Looks like it is the case in your project, if the photos are aligned mainly by the markers and do not have almost any valid tie points with other cameras (you can check it via View Matches dialog).
Title: Re: Depth Maps for newly aligned photos?
Post by: MitchellT on January 14, 2019, 06:54:23 PM
Thank You Alexey,

So here's what happened when I tried to generate the mesh from the same images.

When I used "depth map" as the source, it took almost 24 hours for 220 photos. See attached log file: Jan 11c.txt

When I used "Dense cloud" as the source it took about an hour. About the same number of faces, but the depth map file was MUCH better.

When you look at the log, please notice the many similar error messages such as the one on line 756.

Any advice, recommend actions, or vodka brand?

MitchellT

Title: Re: Depth Maps for newly aligned photos?
Post by: Alexey Pasumansky on January 14, 2019, 07:48:59 PM
Hello MitchellT,

Looks like there are some issues related to the free VRAM when processing on your GTX 580 card (both observed for the depth maps calculations and depth maps based mesh reconstruction).

If you can send the project file with the depth maps, we can run it on out test configurations (similar to yours and optimal) and inform, how log it took for GPU supported stages (additionally, we'll investigate and optimize the VRAM utilization to avoid CPU fallbacks, when it is possible to use GPU for faster calculations).
In case you can send the complete image set and project with the alignment results, we would be able to give the timing for the depth maps calculation stage.
Title: Re: Depth Maps for newly aligned photos?
Post by: MitchellT on January 14, 2019, 08:51:01 PM
Thank you very much Alexey!
I can send you the complete files. How? I send can wetransfer them to you or put em in a dropbox. If you wish to PM me and let me know the preferred method, and the email to use. I had to edit the log file down to 512k just to send to meet the attachment limit on this bb.
MitchellT
Title: Re: Depth Maps for newly aligned photos?
Post by: Alexey Pasumansky on January 15, 2019, 02:17:20 PM
Hello MitchellT,

Thank you for sending the sample data, downloading it now. Will inform you about timing after reprocessing.
Title: Re: Depth Maps for newly aligned photos?
Post by: Alexey Pasumansky on January 18, 2019, 06:11:57 PM
Hello MitchellT,

We have made a comparison test for your project for the mesh based on the High quality depth maps (re-using the alignment from your original project) on the following configurations:
Intel i7 3960X + GTX 680
and
AMD Ryzen Threadripper 2950X + 2x GTX 1080 Ti

The total time for the Build Mesh stage (not including the depth maps calculation) for the first configuration was about 10 hours 30 minutes and for the second - 2 hours and 5 minutes. From this time CPU only part in the beginning and in the end of the job took 1.5 hours for the first configuration and 1 hour for the second one. So the part that uses GPU quite intensively took about 9 hours on GTX 680 and 1 hour on 2x GTX 1080 Ti. In both cases "use CPU" flag has been disabled.

The issue with the memory that you were observing in the log should be fixed in the next update.