Topics

1

Python and Java API / Python API: selecting a specific DEM to use for buildOrthomosaic

« on: June 17, 2024, 08:03:03 PM »

Hello -- I believe that multiple DEMs generated by the `buildDem` step (such as a DTM and DSM) can exist simultaneously in the same project (correct?). How do I specify which one I would like to be used as the basis for the `buildOrthomosaic` step? The options for the `surfaceData` parameter of `buldDem` are `Metashape.DataSource` objects, which include, e.g., `ElevationData`, but not a way to specify *which* elevation data product to use. Is there a way to "activate" the desired `ElevationData` product so that it is used for `buildOrthomosaic`?

Thanks,
Derek

2

General / Incremental images alignement not working

« on: March 24, 2024, 07:55:43 PM »

Hello -- I am attempting to follow the "incremental image alignment" procedure to align a new set of images to an existing set of tie points (sparse cloud). I have selected the "Keep key points" preference, and when I align the second set of images, I disable "Reset current alignment" option.

The behavior is easy to reproduce:
1. Add this folder (https://ucdavis.box.com/s/1ms3sqr13t001k0poiylspt4hl4cn9us) of 174 photos and align.
2. Build and export DEM based on tie points.
3. Add this folder (https://ucdavis.box.com/s/mq9woeeffua83t9688oa81pl6lnak9zz) of 145 photos and align.
4. Build and export DEM based on tie points.

The DEM from Step 4 is shifted relative to the DEM from Step 2, indicating the tie points have been reset and recreated from scratch in Step 3.

I am running this on Ubuntu 22.10. I align using quality Medium, with adaptive camera model fitting. The same thing happens to me in versions 2.1.1, 2.1.0, 1.8.4, and 1.7.1. I've seen multiple reports in the forum over the years of the same issue. I'd appreciate it if Metashape support could attempt to reproduce this issue with my dataset to identify a solution to this bug. Thank you!

3

General / Multiple calibration groups needed for multiple cameras of the same model?

« on: January 03, 2023, 07:01:37 PM »

Hello and happy new year!

I do forest surveys by drone, and at some of my sites I will collect imagery from two drones of the same model (including the same model camera). With two cameras of the same model, is it necessary to use separate calibrations (and thus separate calibration groups)? The photo XMP data from both cameras will specify the same model number, so I believe that Metashape will put them in the same calibration group. I wonder if this is OK, or if I have to separate them into separate groups.

Thank you!

4

General / Metashape errors on NVIDIA A100X with CUDA 11.6

« on: November 10, 2022, 10:57:26 PM »

Hello -- I am attempting to run Metashape on the NSF Jetstream2 GPU virtual machines (https://jetstream-cloud.org/), which use A100X GPUs (partitioned into multiple vGPUs) and which currently run CUDA 11.6. The OS is Ubuntu 22.04 and I am running Metashape 1.8.4 via the Python API.

Almost every Metashape run ends in an error or hang, with errors of different types, at different stages, happening even for identical runs. Sometimes during depth map generation I get the error Exception: Kernel failed: unspecified launch failure (719) at line 329. More commonly though, Metashape will simply hang (during depth map generation or filtering stages), with one CPU core maxed out at 100% and the remainder of CPUs and GPU at 0%. The memory (of the GPU or main RAM) is never anywhere close to exhausted.

I have attempted to disable CUDA, as suggested in another thread for users with similar issues: https://www.agisoft.com/forum/index.php?topic=11771.15
But it did not resolve the errors, it just changed them from CUDA errors to OpenCL errors.

I also attempted to change the tweak "main/depth_max_gpu_multiplier" to 1 (via the python API), but it did not have any effect on processing. It appears that tweak is not recognized by the python API.

Has Agisoft identified any additional solutions to these sorts of errors? Is there any more information I can provide to help identify solutions? Thank you in advance!

5

General / Where to put floating metashape.lic for standalone python module

« on: November 11, 2019, 09:42:39 PM »

Hello -- I am using the Metashape standalone python module on Linux via a floating license. What directories does the Metashape standalone Python module search for the metashape.lic file (which points to the license server)? Is there a way I can modify the directories it searches? So far I have only gotten it to find metashape.lic if it is in my BASH working directory at the time I call Python.