[Gmsh] bug (?) in gmsh-1.65
cag32 at case.edu
Thu Aug 24 05:03:37 CEST 2006
Cristian Tibirna wrote:
> On 23 August 2006 20:42, Christophe Geuzaine wrote:
>>> I must acknowledge that all this doesn't have the feel of a bug, but I
>>> have fallen into it because trying to import with our in-house code the
>>> UNV meshes generated by gmsh-1.65 doesn't give us the same result as with
>>> the same meshes exported by gmsh-1.60.
>> We changed the behaviour a while ago to export all the elements by
>> default, so this looks normal to me.
> OK. But then, is there some option to deactivate the export of the 1d/2d skin
> of 2d/3d meshes? Or how is one to differentiate elements pertaining to the
> skin from elements of the same dimension but not part of the skin (e.g. in a
> mixed mesh that contains both 2d and 3d objects)?
By looking at the line/surface/volume number?
> Thank you for your help
Assistant Professor, Case Western Reserve University, Mathematics
More information about the gmsh