Forum

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - PolarNick

Pages: [1] 2 3 4
1
General / Re: HDD vs SSD - data processing time
« on: August 05, 2022, 10:39:08 AM »
First of all - it is not important where Metashape itself is installed.

It is important where photos and projects files are located. So photos importing was faster thanks to photos located on SSD - Metashape was able to read them one by one much faster than from HDD. And yes, SSD for data storage should lead to faster processing.

2
General / Re: Problems aligning big Dataset in one aligment
« on: August 05, 2022, 10:31:36 AM »
What parameters did you use for alignment in one processing? (you can just click on Tie Points of that attempt and make a screenshot - parameters of alignment will be shown in bottom left corner)

3
General / Re: mesh generation extremely low cpu and gpu usage
« on: August 04, 2022, 11:54:55 AM »
Hi, like you said - it seems to be Input/Ouput-bound (i.e. IO is slow - see also 98% IO in logs). Can you transfer your project from external drive (WB My Book) to local internal disk for processing? (to SSD ideally)

4
General / Re: multi camera system approach for RGB + thermal sensor
« on: July 08, 2022, 12:21:27 PM »
You can't just replace images with images of another resolution (even of the same aspect ratio) because camera alignment includes camera internal parameters calibration and they are dependent on image resolution (and camera FOV, camera distortions and so on).

But I agree with Paulo that you can still reuse camera position and orientation (it will not be very accurate, but probably ok) if cameras were close to each other + were looking in the same direction + both cameras were taken photos at the same time. This script seems to do what you want - https://github.com/agisoft-llc/metashape-scripts/blob/master/src/transfer_orientation.py

5
Python and Java API / Re: align model to model.py without GUI
« on: May 17, 2022, 05:27:11 PM »
Yes, looks like the simplest way.

6
General / Re: Export Cameras Parameters like Colmap
« on: May 17, 2022, 04:49:51 PM »
I think you can follow this script - it parses Agisoft's xml file to pass cameras calibrations into NVIDIA's instant-ngp (NERF) which originally was using Colmap calibrations as input (so its purpose is very close to your request).

7
Python and Java API / Re: align model to model.py without GUI
« on: May 17, 2022, 12:55:59 PM »
Hi, these asserts check that input point clouds (arguments for align_two_point_clouds function) are numpy arrays. You called that function with chunk.models[-1] - which is not a numpy array.

In original script conversion from Metashape's project model representation to numpy array type is implemented via export to ply file and reading it as numpy array.

8
Python and Java API / Re: DepthMap setImage not working
« on: April 13, 2022, 06:05:12 PM »
Hi, removing depth map and then setting it worked for me:

Code: [Select]
ddata = numpy array of depth values in local CS as float32
DM = Metashape.Image.fromstring(ddata.tostring(), ddata.shape[1], ddata.shape[0], ' ', 'F32')
depth_map = chunk.depth_maps[camera]
depth_map.setImage(DM)
del chunk.depth_maps[camera]
chunk.depth_maps[camera] = depth_map

P.S. also please note that setImage has a level argument which is equal to zero by default, but there can be multiple levels (typically three), so maybe it is better to create a fresh one:

Code: [Select]
ddata = numpy array of depth values in local CS as float32
DM = Metashape.Image.fromstring(ddata.tostring(), ddata.shape[1], ddata.shape[0], ' ', 'F32')
depth_map = Metashape.DepthMap()
depth_map.setCalibration(chunk.depth_maps[camera].getCalibration())
depth_map.setImage(DM)
del chunk.depth_maps[camera]
chunk.depth_maps[camera] = depth_map

9
Hi, Python has GIL - Global Interpreter Lock, so python code itself always run on a single core at a time.

But footprints_to_shapes.py and automatic_masking.py runs faster because while their python-part code is still runs on a single CPU core at a time - C++-part of code takes major part of their execution time and can be executed on multiple CPU cores.

For example inside of these calls of project/pickPoint and inside of these calls of image processing operations inside of scipy (they are also written in C++) executions moves from Python-part of code to C++-part of code. And so these calls release Python's GIL at their start and makes multi-core execution possible. They still fallbacks to single-core execution after that, because when they returns to Python-part of code - it is required to acquire GIL back again.

10
Bug Reports / Re: Segmentation fault when checking GPUs
« on: March 11, 2022, 02:00:37 PM »
I afraid that it means that the driver doesn't work properly - clinfo is very stable and just asks driver about available OpenCL devices and their properties.

11
Hi, this worked for me:

LD_LIBRARY_PATH=metashape-pro/python/lib/ metashape-pro/python/bin/python3.8 -m pip install numpy

12
Bug Reports / Re: Segmentation fault when checking GPUs
« on: March 09, 2022, 02:15:55 PM »
What is your GPU? NVIDIA?

Do these programs work?

nvidia-smi
nvidia-settings
clinfo

13
Feature Requests / Re: Iterative Closest Point Algorithm
« on: February 16, 2022, 01:32:29 PM »
Script changes only position of model/point cloud.

Maybe switching From and To objects will work for you? (i.e. aligning point cloud on a 3D model instead of aligning 3D model on a point cloud)

14
Python and Java API / Re: Getting error while using cloud scripts
« on: January 28, 2022, 01:24:46 PM »
Probably NVidia driver 450 installed by the script is not compatible with Ubuntu 20.04.
Please try again on clean instance - the script was updated and now it should use driver 470 for Ubuntu 20.04.

15
General / Re: Face Count, VRAM and Model viewport display.
« on: August 12, 2021, 01:23:24 PM »
+1 for cut-off around 350M

Pages: [1] 2 3 4