dolfin team mailing list archive

["Dag Lindbo" <dag@xxxxxxxx>]

Hi all,

Has anyone looked into the gmsh conversion lately? As far as I know (which
is not much about gmsh, but still), the .msh 2.0 format contains both
lines (order 1) and triangles (order 2) in the 'Elements' list preceeded
by a number indicating how many entries to expect:

$Elements
2131
1 1 2 1 1 4 10
2 1 2 1 1 10 11
...
187 2 2 11 11 462 686 1181
188 2 2 11 11 681 1168 1406
...
2131 3 2 11 11 647 1804 742 1805
$EndElements

dolfin-convert will read this number, but only the triangles. With 0.6.3,
this is causing troubles for me - giving errors of the type 'singular
mapping'. If I remove all order-1 elements from the .msh file and decrese
the number of elements appropriately then the .xml-mesh works fine (after
being converted again).

Am I using gmsh incorrectly? Or is the new mesh more picky about the
indexing and naming of triangles?

Regards,
Dag Lindbo