Assertion "3478972301441" failed at line 720

[Alexey Pasumansky]

Hello djyoung,

Assertion can be related to missing neighbors.

Can you please check, if the problem is resolved in Metashape Pro 2.0.2 build 16001 pre-release, if run on the same project, where the problem has been observed:

Windows: https://s3-eu-west-1.amazonaws.com/download.agisoft.com/metashape-pro_2_0_2_x64.msi
macOS:   https://s3-eu-west-1.amazonaws.com/download.agisoft.com/metashape-pro_2_0_2.dmg
Linux:   https://s3-eu-west-1.amazonaws.com/download.agisoft.com/metashape-pro_2_0_2_amd64.tar.gz

[djyoung]

Thanks Alexey -- but I am experiencing this error using the Metashape python module. Can you send a download link to v2.0.2 of the python module? Thanks.

[Alexey Pasumansky]

Hello djyoung,

Here you go:
Windows: https://s3-eu-west-1.amazonaws.com/download.agisoft.com/Metashape-2.0.2-cp37.cp38.cp39.cp310.cp311-none-win_amd64.whl
macOS:   https://s3-eu-west-1.amazonaws.com/download.agisoft.com/Metashape-2.0.2-cp37.cp38.cp39.cp310.cp311-abi3-macosx_11_0_universal2.macosx_10_13_x86_64.whl
Linux:   https://s3-eu-west-1.amazonaws.com/download.agisoft.com/Metashape-2.0.2-cp37.cp38.cp39.cp310.cp311-abi3-linux_x86_64.whl

[djyoung]

Thanks Alexey, I can confirm that the processing errors I was experiencing using v2.0.0 are now resolved in v2.0.2. Thanks for fixing it.

[bassistas]

Its not resolved, I still get the Assertion failed error in 2.0.2 

[Alexey Pasumansky]

Its not resolved, I still get the Assertion failed error in 2.0.2 

Hello bassistas,

Can you share the complete log from 2.0.2 related to the failure? Either post it here or send to support@agisoft.com.

[bassistas]

Its not resolved, I still get the Assertion failed error in 2.0.2 

Hello bassistas,

Can you share the complete log from 2.0.2 related to the failure? Either post it here or send to support@agisoft.com.

Here is the complete log from 2.0.2 https://drive.google.com/file/d/1KjeacAUi0oZFJiTSe2aEwPsnEr50KQmA/view?usp=share_link
In this project I have 62 laser scans and 927 photos. I managed to align everything but I'm stuck in the build mesh as I always get this error.

[Alexey Pasumansky]

Hello bassistas,

You have Assertion 23671468921001171 in the log, it is a different one.

Can you confirm, if you are working with the newly created project or using some old one? This assertion could be related to rare cases, when the project has been created with the laser scans added in some 2.0.0 version pre-releases.

[bassistas]

Hello bassistas,

You have Assertion 23671468921001171 in the log, it is a different one.

Can you confirm, if you are working with the newly created project or using some old one? This assertion could be related to rare cases, when the project has been created with the laser scans added in some 2.0.0 version pre-releases.

I found what was causing the issue. For some reason one of the imported laser scans was without the panoramic image althought the original e57 has the color information and I opened this exact file on cloudcompare to check if everything is alright. I deleted this laser scan and the process now completed sucesfully. Fortunately the missing laser scan wasnt necessary to cover the area but I cant imagine why all other laser scans imported with their panoramic images and not this one.

[mitchgalea]

Metashape 2.0.2 fixed this error for us

[pima]

Hello Everyone
I just encountered very similar problem.
I have a bunch of scans from leica scanner orinted in Cyclone and exported to e57 separately. I can process all of them in ContextCapture, but some of them (3 out of 20 scans) fail to process to mesh in Agisoft giving error: failed #44 BuildModel.prepairDepthMaps (1/1): Assertion "23671468921001171" failed at line 1149!
It is curious, that same 3 scans in e57 fail to convert to RCP in recap...
Have proceed with some small investigation...
1. changing region in Agisoft does not help (smaller, bigger, different parts of the scan).
2. deleting points not in range, updating, compressing point cloud in Agisoft does not help.
3. eksporting without color or intensity does not help
4. filtering point cloud containing 700.000.000 points giving 0.5mm resolution gives point cloud with 1.700.000.000 :O (something is not right... should be smaller if i understand correctly)
5. importing point cloud with different coordinate precision settings didnt help.
6. using 2.0.2 or 2.0.1 - no difference - fresh projects each time.
7. Two desktops (64 GB RAM and 128 GB ram, different hardware) - same error.
Two of them are in scanners high resolution giving 700.000.000 points, but one of them is in medium resolution with about 200.000.000 points (as all of working scans) so I guess this is not the size problem.
What we noticed is that the scan is processing in Agisoft and Recap if we delete points close to the scanner position in Cyclone before exporting. Is it possible that the problem is too dense point cloud on objects near the scanner??? If i delete same points inside Agisoft (after import) it does not solve the problem - scan is still "faulty" in some way and does not want to process to mesh.
Anyway, the workflow would require to load the scans and just process. Identifing 3 out of 20 scans which is cousing the problem is a bit time consuming (assertation error does not give strait information about the name of scan/scans in project, so I guess it would be best if you could check and solve the problem on importing clouds.
I can send you a link with a sample scan or two. Please provide me an email (or other private masseging system) I can use for passing it.
Best regards

[e.spiridonova]

Hello Everyone
I just encountered very similar problem.
I have a bunch of scans from leica scanner orinted in Cyclone and exported to e57 separately. I can process all of them in ContextCapture, but some of them (3 out of 20 scans) fail to process to mesh in Agisoft giving error: failed #44 BuildModel.prepairDepthMaps (1/1): Assertion "23671468921001171" failed at line 1149!
It is curious, that same 3 scans in e57 fail to convert to RCP in recap...
Have proceed with some small investigation...
1. changing region in Agisoft does not help (smaller, bigger, different parts of the scan).
2. deleting points not in range, updating, compressing point cloud in Agisoft does not help.
3. eksporting without color or intensity does not help
4. filtering point cloud containing 700.000.000 points giving 0.5mm resolution gives point cloud with 1.700.000.000 :O (something is not right... should be smaller if i understand correctly)
5. importing point cloud with different coordinate precision settings didnt help.
6. using 2.0.2 or 2.0.1 - no difference - fresh projects each time.
7. Two desktops (64 GB RAM and 128 GB ram, different hardware) - same error.
Two of them are in scanners high resolution giving 700.000.000 points, but one of them is in medium resolution with about 200.000.000 points (as all of working scans) so I guess this is not the size problem.
What we noticed is that the scan is processing in Agisoft and Recap if we delete points close to the scanner position in Cyclone before exporting. Is it possible that the problem is too dense point cloud on objects near the scanner??? If i delete same points inside Agisoft (after import) it does not solve the problem - scan is still "faulty" in some way and does not want to process to mesh.
Anyway, the workflow would require to load the scans and just process. Identifing 3 out of 20 scans which is cousing the problem is a bit time consuming (assertation error does not give strait information about the name of scan/scans in project, so I guess it would be best if you could check and solve the problem on importing clouds.
I can send you a link with a sample scan or two. Please provide me an email (or other private masseging system) I can use for passing it.
Best regards

Dear pima,

Could you please send us an example of your data set to support@agisoft.com?

[Frode]

I keep running into this problem too with the latest software update. Is there a fix on the way?

[Alexey Pasumansky]

Hello Frode,

Please share the log related to the failed task from its start up to the error message and additionally provide the starting lines from Console pane related to Metashape run.

[Frode]

Is this what you need?