[Gmsh] high order p=10 tetrahedron : a internal node numbering problem ?

[Jean-François Remacle]

Yes, I remember !!!

This bug has recently been fixed : there was a statically allocated table
of 256 nodes and p=10 tets do need 286 nodes . Gmsh 2.5.1 should work.

JF
Le 18 oct. 2011 à 16:18, Pierre Saramito a écrit :

> Hi Everybody,
> 
> I perhaps founded a bug while using high order tetrahedra meshes.
> I just generated by hand the small "tetra_p1.msh" file (attached).
> 
> Then :
>  gmsh -3 -order 10 tetra_p1.msh -o tetra_p10.msh
>       => the file is well generated
> 	  but it could be a problem with the most nested
> 	  internal node numbers: something like a bad
> 	  node permutation.
>  gmsh tetra_p10.msh
>       => core dump.
>  gmsh -check tetra_p10.msh
> 	=> ok
>  gmsh -version
> 	2.5.0 
> 
> Note that for p=9 all is ok:
>  gmsh -3 -order 9 tetra_p1.msh -o tetra_p9.msh
>  gmsh tetra_p9.msh
> 
> Please could you take an eye on the node numbering when p=10 ?
> 
> I take this opportunity to congratulate all the developers
> for the wonderfull features in gmsh.
> 
> Regards,
> 
> Pierre
> -- 
> Pierre.Saramito at imag.fr
> Directeur de Recherche CNRS
> Laboratoire Jean Kuntzmann, Grenoble, France
> http://www-ljk.imag.fr/membres/Pierre.Saramito
> <tetra_p1.msh>_______________________________________________
> gmsh mailing list
> gmsh at geuz.org
> http://www.geuz.org/mailman/listinfo/gmsh

------------------------------------------------------------------
Prof. Jean-Francois Remacle
Universite catholique de Louvain (UCL)
Ecole Polytechnique de Louvain (EPL) - Louvain School of Engineering
Institute of Mechanics, Materials and Civil Engineering (iMMC)
Center for Systems Engineering and Applied Mechanics (CESAME)
Tel : +32-10-472352 -- Mobile : +32-473-909930 

 





-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.geuz.org/pipermail/gmsh/attachments/20111018/0d605d63/attachment.html>