Messages

1

General / Re: Alignment very slow on large project

« on: January 03, 2025, 09:44:12 PM »

I tried reducing both key point and tie point limits and the step that takes a very long time is not affected by this which confirms that it is based on the number of image pairs rather than detected points. The other steps do process much faster though. Thanks for the suggestions.

2

General / Re: Alignment very slow on large project

« on: January 03, 2025, 04:18:23 AM »

Processing isn't stuck. It progresses, just very slowly as it is only using one thread. Have tried reducing key points without any success. I'll try reducing tie points, which may help as it seems to be related to the number of matches. I thought this might have been the number of image matches but it may be tie point matches.

Sorry, I don't have many details on the camera used for the project other than it is ~4MP and a very wide field of view, ~180 deg.

3

General / Re: Alignment very slow on large project

« on: December 23, 2024, 09:30:06 PM »

Thanks for your thoughts. I do use multiple nodes on each computer, but the stage that takes forever can only be done by a single worker. The other steps in the alignment phase do benefit from the additional workers. The problem seems to be exponential with the number of images. Projects with ~20,000 images are fine and make it through this step fairly quickly and then move on to steps where multiple workers are beneficial. However, a project with ~70,000 images has been stuck in this step for almost a week and using hardly any resources.

4

General / Re: Alignment very slow on large project

« on: December 19, 2024, 11:11:15 PM »

And how does your project look like? It is drone photogrammetry of large area, or ground photogrammetry of some building, or...?

It is underwater photogrammetry of a 3D object. The area is about 100m x 20m. Smaller projects that are ~20,000 images or less tend to get through that step relatively quickly.

5

General / Re: Alignment very slow on large project

« on: December 19, 2024, 04:47:49 PM »

In network scenario it seem to be a lot of work to join small partly results to one chunk, especially on large project.
Try to spawn more local workers on each node, it should speed up single threaded tasks.

I tried running this not in network mode and after getting to the same step it is still very slow and barely using any resources so it doesn't seem this is related to network processing.

6

General / Re: Alignment very slow on large project

« on: December 17, 2024, 10:38:37 PM »

Can you at least decrease keypoint limit to 40k or even 20-30k? Would it be sufficient for your project? Also tiepoints limit 6000...for my projects 2000-4000 was fully enough.

Reducing the tie point limit did not reduce the number of pairs selected. I expect that reducing the key point limit won't either. The pairs selected likely has to do with the image pairs for matching, which has to do with the number of images and overlap rather than tie points or key points. If that is the case then I don't see any way to speed things up other than reducing the number of images.

7

General / Re: Alignment very slow on large project

« on: December 17, 2024, 02:05:30 AM »

Have tried on an i9 11900k and a threadripper 7960x. With both systems it hardly uses any CPU.

8

General / Re: Alignment very slow on large project

« on: December 16, 2024, 05:41:33 PM »

Thanks, I will try reducing and see if it has any affect on model quality for this project.

9

General / Re: Alignment very slow on large project

« on: December 16, 2024, 05:32:44 PM »

Thanks for the suggestion. I am able to do this on some of the steps but unfortunately on this step there is only 1/1 worker. It doesn't seem to split the step into multiple parts.

10

General / Re: Alignment very slow on large project

« on: December 16, 2024, 04:58:40 PM »

Here is the console at this point:

MatchPhotos.select (1/1): downscale = 1, subtask = select, generic_preselection = on, reference_preselection = off, filter_mask = off, mask_tiepoints = off, filter_stationary_points = off, keypoint_limit = 60000, keypoint_limit_per_mpx = 1000, tiepoint_limit = 6000, guided_matching = off, exclude_corners = off, data_folder = //Be7960x/e/DVDSSP/PS/DVDSSP.files/0/0/point_cloud
loaded matching data in 0.01 sec
loaded matching partition in 24.507 sec
loaded matches in 280.017 sec
492448668 pairs selected in 19.8 sec

It will sit here for a long time and then move to "setting point indices", which also takes a very long time

11

General / Re: Alignment very slow on large project

« on: December 16, 2024, 04:56:32 PM »

The only activity I see at this stage is a single core/thread near 100%. There is no GPU or network utilization. Before and after this step resources are well used.

12

General / Alignment very slow on large project

« on: December 16, 2024, 03:24:15 PM »

Hello,

I am processing very large projects with 60-70k images. I have successfully processed a few models of this size already using network mode and two nodes but there is a step in the alignment phase that is very slow. After detecting points, it comes to "x pairs selected in..." and then " setting point indices". This step takes days to complete and uses almost no resources on the computer. Is there a way to speed this up? The rest of the alignment processes as expected, using the resources available. I have tried using the --inprocess flag but it hasn't made a noticeable difference.

Thank you

13

General / Re: Agisoft Metashape 2.2.0 pre-release

« on: December 02, 2024, 12:15:28 AM »

.

14

General / Re: Agisoft Metashape 2.2.0 pre-release

« on: November 29, 2024, 03:57:06 PM »

When I start a worker in network mode the Agisoft startup screen is displayed but never disappears. It remains on the screen in front of everything making it difficult to see anything. It says Loading geoids... Is this expected behavior?

15

General / Re: Agisoft Metashape 2.2.0 pre-release

« on: November 19, 2024, 05:00:37 PM »

I am having crashing issues when processing a point cloud at ultra high quality. Using rtx4090 with driver 566.14 and Agisoft 2.2.0. Is this related to the Nvidia driver bug? System event viewer has these logs below which seems to indicated GPU issues.

------------------------------------------------------------------------------

The description for Event ID 13 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

\Device\Video3
Graphics FECS Exception: Logging error 0x2

The message resource is present but the message was not found in the message table

-----------------------------------------------------------------------------------------------------------------------------------------------------------

Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0

Problem signature:
P1: 141
P2: ffffc50bbce63220
P3: fffff8036f22e650
P4: 0
P5: ffffc50ba8577080
P6: 10_0_26100
P7: 0_0
P8: 256_1
P9:
P10:

Attached files:
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20241106-0516.dmp
\\?\C:\WINDOWS\SystemTemp\WER-971167921-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.fb5374e3-ce76-46cf-a64e-e29b0f5012c8.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.54a745bb-79dd-4b01-ba2b-dd1f1e4781f4.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.31b9b4de-900f-4ab2-ae0d-db1c46c068a0.tmp.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.c4e29d9d-ce8b-498d-80bf-fac204cb09cb.tmp.xml

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_141_77ecd6884fb27125f72a5698c0c587c869969d_00000000_caa5711e-1e6e-42f0-ae62-6582624baaae

Analysis symbol:
Rechecking for solution: 0
Report Id: caa5711e-1e6e-42f0-ae62-6582624baaae
Report Status: 2049
Hashed bucket:
Cab Guid: 0