Break down of the console info for different phases.
I am processing a data set currently and it is taking a long time. I checked for bad cameras everything seems to be fine. It is not hanging on a single phase in fact it seems to be going along albeit very slowly. I have the console up as I am certain the progress bar that is given is not what I am looking at time wise. I am really curious in the information that is being given to me during the texturing as I don't see any info in the help window.
example:
Processing started.
Processing finished in 66.972572 seconds.
P(148,258),MP(133,1024,17186),IM(111,111)
Loading of 111 images started.
111 images loaded in 136.143216 seconds.
Loading and processing of metadata started.
Metadata loaded and processed in 2.991161
----end of example
So I can gather the IM(xxx,xxx) is the number of images matched/total and I think the P(yyy,yyy) is referencing the Part count. Though I don't understand the last metric. Also why I left my office at 5:00pm and when I got back at 9:00am it had only run 16% further. The final bar that reads...>> Texturing Model 39% completed. Time remaining 113719 seconds.
This is far from the largest data set that I have ran through CR so I am at a loss why it is taking so long. I do have a decent amount of RAM 128GB. I am using M.2 drives for read/write that are fast enough and large enough. So I am not currently worried about a out of memory our diskspace error.
This data set is 2905 images from 3 camera types a 2 drones and a DSLR. We also have 1 rig of an .e57 from 20 scan locations around the site. So the total number of inputs is 3049 with only 3001 aligning automatically. The mesh size is 474.9M tris. the quality of the mesh texture is 100% with a 93% utilization. This is a very large area capture including some nice detail shots of the focal point of the capture area.
Our plan is to host the tiled data on our online viewer that can definitely handle the data size so please no suggestions of simplify the mesh because I did a test down to 125M tris and I was not satisfied with the mesh calcuated.
-
Hi ecko360RC,
about your first question, P is for Model parts, IM is for used images and MP is internal note for our developers.
What were your texturing settings? Are you using also laser scans for texturing?
Texturing requires 500 bytes of storage for each triangle, so your large model would have needed about 240 GB free space on your cache disc. Also, this could be the result of using 3 different cameras.
How did you simplified your big model? Did you do it by incremental steps or in one step?
-
Hi Ondrej Trhan CR,
Thanks for getting back to me. I will try to answer as concisely as possible.
Texture Settings
Fixed Texel Size, 46 Count, 16k x 16k, 2 texel gutter, 93% utilization, .005919 units per texel, 100% quality, .005919 units per texel, High Quality, 1 image downscale for depth maps.
Laser scans are not being used for texturing. My cache disc has alot of space so not worried about that at the moment.
My big model has only been clipped and removed the marginal triangles, I removed parts that were not connected the the main component, I also tightened the area of the reconstruction so I didnt have too many bizarre areas. I did no major simplification as I wanted as much of the mesh as possible to be from the initial High detail reconstruction. When I did the simplification it was 1 large step but it isnt a big deal just wondering why it is taking so long. It has now been running for 2.5 days and only at 59% complete. 106055 seconds remain but as I showed in my previous post the calculation is way off even in the log. only lose 6000 seconds in a day when really it should remove 86400 seconds.
Please sign in to leave a comment.
Comments
3 comments