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 - Paulo

Pages: [1] 2 3 ... 89
1
General / Re: Hardware for Large Scale Projects
« on: Today at 02:35:49 PM »
With 180k photos the key will be good utilization of HW. I see the fastest way by using network processing locally on single machine(maybe two).
If you create several local instances of running metashape, you can e.g. greatly speed up phase of detection points from photos, which is important in case of 180000 photos.
These local instances are helping to keep CPU and GPU utilized ~100% all the time without drops.

Instead of buying AMD Ryzen Threadripper PRO 7995WX you can spend much better money and buy two computers with 32c64t Threadripper 7975WX(higher multicore frequency) and RTX4090.

What will be important during processing is manually assigning the total number of nodes in each processing phase.
For example:
First phase - detecting points needs maybe 10-20 concurently running metashape instances to feed enough one RTX4090...so you enable 10-20 nodes.
After this pahse, matching points is more excesive task for GPU, so you will keep only ~3 nodes active, or maybe few more if you see GPU is not utilized without % drops. More instances would feed too much GPU.
During depth maps generation, which is pure GPU task, maybe two GPUs would be useful.

So my final advise is, buy one computer and if it will be fully utilized locally during network processing, then you can buy exactly another one to half the processing time...if needed. Or you can buy second GPU if you will see, that depth maps gen. is still slow.

It could be beneficial to buy two RTX4080 instead of one 4090, from performance reason, but that is only my assumption.

Hello Bzuco,

your suggestion is very interesting. As I am not a computer expert, can you explain how you create several local nodes of Metashape to work in network... Would be very helpful to have a step by step guide for such setup.

Thanks again for your insights on computer use!

2
Hello Yvo,

I would suggest to look at following reference list https://agisoft.freshdesk.com/support/solutions/articles/31000156964-references-list#Depth-Map%C2%A0.

In particular sections relative to  Depth Maps and Mesh... Should give you a better idea of what is behind these processes.

For image capture tips, see https://agisoft.freshdesk.com/support/solutions/folders/31000117943

3
General / Re: Image Alignment and Inertial Reference Data
« on: April 23, 2024, 04:05:47 AM »
Hello Chris,

a few questions for u:
  • What is the accuracy of your GPS/IMU data?
  • is the plane taking the photos in one line?
  • if so if you can share an example of one plane pass then I could align it and give recommendations?

4
General / Re: Splitting up a multicam rig after the alignment process?
« on: April 17, 2024, 02:16:11 AM »
Hi Martin,

you can certainly access and export the slave cameras along with master. If you have a 5 camera rig with 1 master and 4 slaves, then chunk.cmeras[0] is master and chunk.cameras[n] with n = 1 to 4 are slaves....etc...

5
General / Re: GCP WITH DJI L1 POINT CLOUD
« on: April 16, 2024, 03:29:29 PM »
Hi Lorenzo,

my email is pap1956@gmail.com.

Looking forward to see your data.

If the Terra generated las cloud has a trajectory file, please include....

6
General / Re: GCP WITH DJI L1 POINT CLOUD
« on: April 15, 2024, 05:33:09 PM »
Hi Lorenzo,

if it is possible to share a las from L1 sensor and corresponding GCPs and I could certainly help you in this....

7
Python and Java API / Re: Apply patch on multiple shapes
« on: April 10, 2024, 08:48:31 PM »
lorenzoo,

you must define s as your selected shape as:
Code: [Select]
s = [s for s in chunk,shapes if s.selected][0]
s.geometry.coordinates[0]

8
Ok Jake.

then when you go back from CRS to internal you should  change:
Code: [Select]
bb_size = T.inv().mulp(crs.unproject(size_CRS))with:
Code: [Select]
bb_size = T.inv.scale() * size_CRS

9
Hello Matt,

at first glance, the CRS_size parameter is wrongly calculated:
Code: [Select]
size_CRS = chunk.crs.project(T.mulp(size)) # vector with point coordinates in CRSshould be changed to:
Code: [Select]
size_CRS = T.scale()*size # BB box size in real world CRS
Try and see if it can work...

10
General / Re: DEM Fill Tool
« on: April 09, 2024, 06:39:09 PM »
Dave,

seems to be some sort of bug. In constant interpolation if you use pick button and click a point just outside the red mask, the value should update and give better results...

11
General / Re: RTK Positioning accuracy with Mavic 3E
« on: April 09, 2024, 06:34:20 PM »
Quite right, Dieter

and it also helps us learn a few more deutsch words...

12
Python and Java API / Re: Apply patch on multiple shapes
« on: April 09, 2024, 02:57:27 PM »
Hi,

Yes the coordinates of shape are now defined by shape.geometry.coordinates[0]... See attachment...

13
General / Re: RTK Positioning accuracy with Mavic 3E
« on: April 09, 2024, 02:44:09 PM »
Das ist right....

My Deutch is not up to par!

14
General / Re: DEM Fill Tool
« on: April 09, 2024, 02:42:35 PM »
Strange Dave,

can you print the shape vertex coordinates? And what is shapes crs? same as dem CRS?

15
Hi Jake,

In my book, I would use  PPP (minimum 4 h) to obtain a updated and precise base station coordinates,

Then calculate the shift from original to updated position and apply this to all camera reference coordinates and then redo the workflow to generate orto...

Hope this can be helpful,

Pages: [1] 2 3 ... 89