[giulio romano]

Hello to everyone, I'm new to this forum and I would ask some information about the mesh usage in SU2. I'm performing some calculation on the fuselage of an airplage. To generate the hybrid mesh I'm using GMSH but when I try to run the simulation in SU2 I obtain this error:

Error in "void CPhysicalGeometry:istributeColoring(const CConfig*, CGeometry*)":

-------------------------------------------------------------------------
Mismatch between NPOIN and number of points listed in mesh file.
Please check the mesh file for correctness.

------------------------------ Error Exit -------------------------------

application called MPI_Abort(MPI_COMM_WORLD, 1) - process 0
[unset]: write_line error; fd=-1 buf=:cmd=abort exitcode=1
:
system msg for write_line failure : Bad file descriptor

Does someone know what is this issue about and if it is a problem in the mesh generation or in the reading of the mesh from SU2? There is a way to solve it while keep on using GMSH ? I attach the cfg file and the python script for the mesh to this post, so you can better understand the issue.
Thank you in advance

[A.Roy]

Are you able to post either the mesh file or the iges geometry referenced in the gmsh python script to generate the mesh?

[bigfootedrockmidget]

Common problem with such imported geometries is that it usually only imports the surface and the elements/cells were not generated in gmsh. Can you check in gmsh if you have any internal elements? You can also check in the su2 file if there are any elements (NELEM=0) in the file.

[giulio romano]

Originally Posted by A.Roy

Are you able to post either the mesh file or the iges geometry referenced in the gmsh python script to generate the mesh?

Hello thank you for the reply here it is the iges file.

[giulio romano]

Originally Posted by bigfootedrockmidget

Common problem with such imported geometries is that it usually only imports the surface and the elements/cells were not generated in gmsh. Can you check in gmsh if you have any internal elements? You can also check in the su2 file if there are any elements (NELEM=0) in the file.

Hello thank you for the reply. I checked the SU2 file and the NELEMENT is not 0. But by looking at the SU2 mesh file I realized that the NPOIN = 50342 in my case but there are only 50341 points written below, i tryed to change in the mesh file NPOIN=50341 but SU2 gave me a different error:

"/usr/include/c++/8/bits/stl_vector.h:932: std::vector<_Tp, _Alloc>::reference std::vector<_Tp, _Alloc>:perator[](std::vector<_Tp, _Alloc>::size_type) [with _Tp = long unsigned int; _Alloc = std::allocator<long unsigned int>; std::vector<_Tp, _Alloc>::reference = long unsigned int&; std::vector<_Tp, _Alloc>::size_type = long unsigned int]: Assertion '__builtin_expect(__n < this->size(), true)' failed.
[1] 667514 abort (core dumped) SU2_CFD case15_BLI_fuselage_test3_GMSH.cfg"

How can I check in GMSH if I have any internal elements ?

I'm sorry that I can't attach to this post the mesh in SU2 and msh format so you can visualize them, because they are too large.

[bigfootedrockmidget]

gmsh also uses helper points to construct your mesh, for instance the center of a circle is a helper point. Usually, these points are ignored if you deselect the option 'save all elements'. If this option is already deselected, then you could go through the su2 mesh points and check if there is a point that is not used in the mesh. I posted a python script for this a while ago on the forum. But the best thing is to solve it in gmsh.