Agisoft Metashape
Agisoft Metashape => General => Topic started by: Dmitry Semyonov on November 29, 2017, 02:30:26 PM
-
New reconstruction method with strict volumetric masking support was released in PhotoScan 1.4.0 pre-release (http://www.agisoft.com/forum/index.php?topic=7730.0).
You can read tutorial and tool description and take a look at examples in blog post (http://www.agisoft.com/index.php?id=48).
More examples available here - Photoscan 1.4.0 - New Feature Comparisons (http://www.agisoft.com/forum/index.php?topic=7961.0).
Please let us know if you have any problems using this tool.
-
Dmitry > is this method generating the depth map on its own to use them or is it still necessary to build a whole dense cloud to produce them ? Do you have any formula to estimate the memory needed ?
-
Hello JRM,
New mesh reconstruction method is building depth maps itself, so it is not necessary to generate the dense cloud.
Note that currently this new method is utilizing Mild filtering for the depth maps generation, it means that you can only re-use depth maps, if they have been generated using Mild option (and are kept in the project, of course).
-
Hello,
very promising new feature!
However, the volumetric strict masking does dot work using API command buildModel as seen from console extract:
chunk.buildModel(surface=PhotoScan.Arbitrary, interpolation=PhotoScan.EnabledInterpolation, source=PhotoScan.DepthMapsData, quality=PhotoScan.HighQuality, volumetric_masks=True, vertex_colors = False)
2017-12-01 10:02:45 BuildModel: surface type = Arbitrary, source data = Depth maps, quality = High, depth filtering = Mild, volumetric masking = 0
It would also be interesting to assure depth maps are kept in document after this command as it would be needed for example to refine the masked images manually and then rerun buildModel in auto process without need to re generate depth maps and thus save time.
Thanks for your great work!
-
Hello Paul,
If "Keep depth maps" option is turned on in the Advanced Preferences of PhotoScan, the depth maps will be stored in the project when new mesh generation method is used (already in build 5432).
volumetric_masks API parameter will be fixed in the next update.
-
Hello Alexey,
yes I have found that when new mesh method is used in GUI, the depth maps are saved (with option activated in Advanced Preferences). However, when using new mesh creation in API then the depth maps are not saved in project....
Waiting for next update, then...
-
Hello Paul,
Ok, understood, we'll also add keep depth maps argument for new mesh generation method call from API.
-
Very good,
Spasiba Alexey
I just checked the latest 1.4 release and the strict volumetric mesking is working when using API method
chunk.buildModel(surface=PhotoScan.Arbitrary, interpolation=PhotoScan.EnabledInterpolation, source=PhotoScan.DepthMapsData, quality=PhotoScan.HighQuality, volumetric_masks=True, vertex_colors = False)
However the depth maps are not kept with this API command while the maps are kept when using GUI Create mesh....
I just saw the parameter keep_depth in new bUild Model and it works fine!
-
Hi there.
Which workflow do you suggest if let's say I want to create a thin model with this workflow, but still have markers and scale bars? I have a propeller blade I want to create a scaled model of.
EDIT: Think I got it, doesn't really change anything. Added markers and scale after model was finished and did another alignment and update, and it seems like it's working.
-
For the new model, I made a simple comparison.
The PhotoScan model is more elaborate, but lost its base and has 3 holes.
-
Hello ruyi7952,
Have you generated tiled model using new meshing method or have built it from mesh?
-
Hello Alexey
I have used new meshing method
-
Hello ruyi7952,
Which quality settings have you used? And have you removed the masks from the project? The default masks cover the stand, so it wouldn't be reconstructed neither in dense cloud, not in mesh.
-
Hello Alexey
I created a new project, using the default parameters.