heal auto_remove_duplicates

Submitted by hansmannb on Wed, 01/08/2014 - 10:07

Hej guys.

I'm trying to creat a mesh but instead i get this ERROR:

...
Mesh cad: element id 31375 (line 219669) has 6 neighs, but only 5 expected
Mesh cad: element id 31598 (line 221230) has 6 neighs, but only 5 expected
Mesh cad: element id 31502 (line 220558) has 6 neighs, but only 5 expected
ERROR: Mesh cad: elements 6049 and 6050 (lines 42349 and 42356) are duplicate
ERROR on proc 4: Fix mesh: Bad mesh, cannot continue. You can try re-running wit
h 'heal auto_remove_duplicates' (e:\002_liggghts_paraview\liggghts-public_238\sr
c\surface_mesh_I.h:456)

job aborted:
rank: node: exit code[: error message]
0: NBAL-PC688: 123
1: NBAL-PC688: 123
2: NBAL-PC688: 123
3: NBAL-PC688: 123
4: NBAL-PC688: 1: process 4 exited without calling finalize
5: NBAL-PC688: 123

Does someone know about "heal auto_remove_duplicates" or another solution for this problem?

Regards.

ckloss_ | Mon, 01/13/2014 - 15:08

Hi hansmannb,

it seems that the mesh you are using has duplicate elements, which means that the mesh is somewhat corrupt. There are some tools available (eg meshlab) that may help you to clean it, or you try another way to create the mesh.

Best wishes
Christoph

peter_weatherhead | Sat, 04/26/2014 - 15:36

Hi,

I too have encountered this problem when two different stl files had overlapping elements (accidentally). I found looking at the imported meshes in paraview and turning them on / off one by one helped. But also issuing the HEAL AUTO_REMOVE_DUPLICATES keyword as part of the import statement enabled the simulation to run without need to rectify the mesh issues. Obviously if the meshes have different properties etc this probably isn't the best approach.

Cheers,

Pete

ckloss's picture

ckloss | Wed, 04/30/2014 - 13:32

Hi hansmannb and Pete,

auto_remove_duplicates can delete elements that are 1:1 duplicates, but it doesn't do something if there are too many neighbors. In most of these cases, displaying the issue in paraview and going back to the meshing step will resolve the problem

Christoph