[Gmsh] cgns: Segmentation fault
vitkecar at gmail.com
Sun May 16 20:16:14 CEST 2010
Sorry, I know the screenshot is confusing. I just couldn't find a
better way to visualize it. Also sorry for a wrong subject.
Imagine that you start from a nice tetrahedron and divide one of it's
edges into some 10 segments, connect them with the opposite edge, and
in this way you divide your tetrahedron into 10 thin tetrahedra. Why
would something like this happen? Certainly such mesh is of a very
poor quality, and it shouldn't be, because the geometry is so simple.
So I consider this a bug. One funny thing is that I get the same mesh
no matter which one of the meshing algorithms I use (Advancing Front
etc), but only if I generate the mesh from the command line. Optimize
option does solve the problem.
On 5/16/10, David Colignon <David.Colignon at ulg.ac.be> wrote:
> Hi Dragan,
> sorry, I am not able to see any peculiar detail in your screenshot...
> But can you try to add the option "-optimize" on the command line to improve
> the quality of the mesh ?
> David Colignon, Ph.D.
> Collaborateur Logistique du F.R.S.-FNRS
> CÉCI - Consortium des Équipements de Calcul Intensif
> ACE - Applied & Computational Electromagnetics
> Institut Montefiore B28
> Université de Liège
> 4000 Liège - BELGIQUE
> Tél: +32 (0)4 366 37 32
> Fax: +32 (0)4 366 29 10
> WWW: http://hpc.montefiore.ulg.ac.be/
> Agenda: http://www.google.com/calendar/embed?src=david.colignon%40gmail.com
> On 14/05/10 14:58, Dragan Vidovic wrote:
>> By meshing a simple unit cube using
>> gmsh -3 -clmax 0.05 unitcubeUns.geo
>> I obtained a mesh with a peculiar detail that you can see in the
>> attached screenshot. It seems like gmsh was slicing one single
>> tetrahedron. This causes certain death to my FV code. Is there any way
>> to make sure that this does not happen?
>> gmsh mailing list
>> gmsh at geuz.org
More information about the gmsh