Assertion "3478972301441" failed at line 720

[kasten.mega]

Hello! I'm using Agisoft Metashape 2.0.0 and have now run into the Assertion failed at line error when trying to build a dense point cloud. I've checked and my GPU drivers are all up to date? Log attached. Thank you in advance!

[kasten.mega]

Just a quick update, I have no explanation for why this worked, but! Originally, I had aligned my photos, then used gradual selection to use the 'Reconstruction Uncertainty' function. I had then used the Optimise camera alignment, with all but k4 checked. This is when I tried to create a dense cloud and ran into the above error.

I did an extra 'align photos', then followed with build point cloud, and now it's working! So I'm not sure why but hope it helps someone.

[Alexey Pasumansky]

Hello kasten.mega,

Can you please share the project with the alignment results only (estimated camera locations and tie points) to support@agisoft.com?

[marlinmm]

Just a quick update, I have no explanation for why this worked, but! Originally, I had aligned my photos, then used gradual selection to use the 'Reconstruction Uncertainty' function. I had then used the Optimise camera alignment, with all but k4 checked. This is when I tried to create a dense cloud and ran into the above error.

I did an extra 'align photos', then followed with build point cloud, and now it's working! So I'm not sure why but hope it helps someone.

I have the same issue and did the same steps (I selected by reprojection error). I opened the project in Metashape 1.8.4 and there it works... So somehow I would still blame version 2.0.0.
Would be great to get a real explaination or fix.

And for me the extra step with the second aligment didnt work either

Best regards

[Alexey Pasumansky]

Hello marlinmm,

Maybe you can share the project with the alignment results and filtered out points, so that we could reproduce the issue on our side?

[marlinmm]

Do you mean the console log or the entire project including the data?

[Alexey Pasumansky]

Hello marlinmm,

For initial analysis it would be sufficient to have project (could be saved as a single file in PSZ format) with estimated camera locations, markers, tie points and thumbnails. Other data (if any) can be removed from the project copy before sending. Project file can be shared as a download link via any convenient file transfer service.

[JacquesMDC]

Hi, I faced the same problem, with the same error message than Kasten.Mega. I fellowed its solution : it works untill now ; I'm building dense points cloud. Hope I wil not have further stops in the workflow 

[Tristan_D]

Hello,

I am having this issue after upgrading to v2.0. Is there a known solution?

[remco.kootstra]

Just a quick update, I have no explanation for why this worked, but! Originally, I had aligned my photos, then used gradual selection to use the 'Reconstruction Uncertainty' function. I had then used the Optimise camera alignment, with all but k4 checked. This is when I tried to create a dense cloud and ran into the above error.

I did an extra 'align photos', then followed with build point cloud, and now it's working! So I'm not sure why but hope it helps someone.

I'm running into the same issue. After allignment I used the gradual selection to remove some of the uncertainties. When I tried to generate a dense cloud I get the same 'Assertion error message'.
I also generated a dense cloud without removing the uncertanties with the gradual selection tool but then there are no problems.

In my opinion something in V2.0 goes wrong after removing some uncertainties with the gradual selection tool.

Regards,

Remco

[michael.jarvis@rochester.]

Hi,  I am getting this error as well, using Metashape Pro 2.0.0.15597, with an RTX 3070 and the latest Nvidia driver 528.49.  I too did Gradual Selection culling first (Accuracy, Reprojection Uncertainty, Reprojection error) before getting this error.  I tried to do a second align photos (per another user's suggestion) but that did not work.  Screen shot of the error screen with project specs attached, along with the log. I also got a different but similar error on an earlier build attempt.

 It's a big job, so sending you the whole psx would be cumbersome.

Thanks, 
Mike

[Tristan_D]

Hello,


This subject was brought up in another post, but no clear solution was arrived at.


I have recently upgraded to metashape 2.0, and I keep running into the "Assertion "3478972301441" failed at line 720!" error while building dense point clouds. I have been able to get past this by making sure I optimize camera alignment after and gradual selection and tie point removal. However, I am now using a co-alignment methodology for change detection, which involves aligning all imagery from several dates of the same location, aligning all of the imagery as one chunk, duplicating the chunk and deleting all cameras and tie point except those from a single date. One each date has been isolated in it's own chunk, I do not want to optimize camera alignment because I want to keep them consistent between chunks. But this results in the  "Assertion "3478972301441" failed at line 720!" error.



Could you agisoft support or any users please advise me on how to overcome this error?


Thank you,



Tristan

[Alexey Pasumansky]

Hello Tristan,

We were not yet able to reproduce the issue on our side, as we have got only one dataset related to this assertion provided by user. And the problem couldn't be reproduced on this only project that we have received.

If you are getting stable assertion for some project, it would be helpful, if you can share that project to us together with the related images.

[mitchgalea]

I get the same error on my project, I've tested it on both Metashape 2.0.0 and Metashape 2.0.1

[djyoung]

I am experiencing this same frustrating error in v2.0, also with a workflow that includes removal of tie points using gradual selection. My workflow uses the python API.

I'm not able to send project files to let others reproduce this, because when I try to reproduce it myself using a project file from a previously failed workflow (saved after building depth maps) and running the "build point cloud" step (using the GUI), it works.

I wonder if it has to do with the fact that some cameras have no neighbors? Here's the progress text from the start of the "build point cloud" step in case it helps.

Generating depth maps...
Preparing 2006 cameras info...
cameras data loaded in 1.06719 s
cameras graph built in 0.692246 s
filtering neighbors with too low common points, threshold=50...
Camera 577 has no neighbors
Camera 1184 has no neighbors
avg neighbors before -> after filtering: 294.991 -> 112.525 (62% filtered out)
limiting neighbors to 16 best...
avg neighbors before -> after filtering: 112.525 -> 15.984 (86% filtered out)
neighbors number min/1%/10%/median/90%/99%/max: 0, 16, 16, median=16, 16, 16, 16
cameras info prepared in 16.8615 s
saved cameras info in 0.035684
Partitioning 2006 cameras...
number of mini clusters: 41
41 groups: avg_ref=48.9268 avg_neighb=92.3659 total_io=289%
max_ref=50 max_neighb=160 max_total=207
cameras partitioned in 0.072118 s
saved depth map partition in 0.001658 sec
loaded cameras info in 0.025856
loaded depth map partition in 6.8e-05 sec
already partitioned (47<=50 ref cameras, 100<=200 neighb cameras)
group 1/1: preparing 147 cameras images...
tie points loaded in 0.010106 s
Found 1 GPUs in 0.000266 sec (CUDA: 0.000134 sec, OpenCL: 0.00011 sec)
Using device: GRID A100X-40C, 108 compute units, free memory: 36887/40955 MB, compute capability 8.0
  driver/runtime CUDA: 12000/10010
  max work group size 1024
  max work item sizes [1024, 1024, 64]
group 1/1: cameras images prepared in 13.2945 s
group 1/1: 147 x frame
group 1/1: 147 x uint8
group 1/1: expected peak VRAM usage: 236 MB (64 MB max alloc, 2736x2736 mipmap texture, 16 max neighbors)
Found 1 GPUs in 0.000276 sec (CUDA: 0.000139 sec, OpenCL: 0.000119 sec)
Using device: GRID A100X-40C, 108 compute units, free memory: 36887/40955 MB, compute capability 8.0
  driver/runtime CUDA: 12000/10010
  max work group size 1024
  max work item sizes [1024, 1024, 64]
Using device 'GRID A100X-40C' in concurrent. (2 times)
[GPU 1] group 1/1: estimating depth map for 1/47 camera 6 (16 neighbs)...
[GPU 2] group 1/1: estimating depth map for 2/47 camera 7 (16 neighbs)...
[GPU 1] Camera 6 samples after final filtering: 85% (6.81738 avg inliers) = 100% - 0% (not matched) - 4% (bad matched) - 0% (no neighbors) - 1% (no cost neighbors) - 6% (inconsistent normal) - 0% (estimated bad angle) - 0% (found bad angle) - 3% (speckles filtering)
[GPU 1] Camera 6: level #4/4 (x4 downscale: 1368x912, image blowup: 2736x1824) done in 0.435811 s = 30% propagation + 34% refinement + 22% filtering + 0% smoothing
Peak VRAM usage updated: Camera 6 (16 neihbs): 235 MB = 100 MB gpu_neighbImages (43%) + 64 MB gpu_tmp_hypo_ni_cost (27%) + 12 MB gpu_tmp_normal (5%) + 9 MB gpu_neighbMasks (4%) + 7 MB gpu_mipmapNeighbImage (3%) + 4 MB gpu_refImage (2%) + 4 MB gpu_depth_map (2%) + 4 MB gpu_cost_map (2%) + 4 MB gpu_coarse_depth_map_radius (2%) + 4 MB gpu_coarse_depth_map (2%)
[GPU 2] Camera 7 samples after final filtering: 86% (6.84724 avg inliers) = 100% - 0% (not matched) - 4% (bad matched) - 0% (no neighbors) - 1% (no cost neighbors) - 6% (inconsistent normal) - 0% (estimated bad angle) - 0% (found bad angle) - 3% (speckles filtering)