[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Getfem-users] gmsh, getFem, regions

From: Ronan Perrussel
Subject: Re: [Getfem-users] gmsh, getFem, regions
Date: Thu, 16 Jul 2009 11:14:56 +0200
User-agent: Thunderbird (X11/20090409)

Dear Umut,

this mapping from n to n+1000 has been removed recently (at least on the svn version which I used; could someone confirm it is also true on the version available on the website?)
But I am not sure the comments have been corrected everywhere in the code.

On the current version, the region number for your N-1 dimensional region should be 2...

Best regards,

Umut Tabak a écrit :
Dear all,

I checked the mailing list and the documentation of the for an import operation in getFem.

I am a bit confused about the msh import from gmsh, more specifically on the import of the physical regions. I am also trying to check from the source code but could not find the answer yet. I have defined my physical volume and surface in gmsh and marked them as 1 and 2 respectively, but when I use the import_mesh function, I can see with a simple check like: by taking into account also, directly from import_mesh.h

   /* For a mesh of dimension N, getfem builds a mesh with the
      convexes listed in the gmsh file whose dimension are N, the
      convexes of dim N-1 are used to tag "region" of faces,
      according to their gmsh "physical region number" (physical
      region number 'n' is mapped to the getfem region '1000+n'), and
      the convexes of lower dimension are ignored.

     std::cout << "The mesh has region 1 defined" << std::endl;
     std::cout << "The mesh has region 2 defined" << std::endl;

I only have region 1, the volume, what am I missing for region 2, the face(or 1002 in getFem mapping)?

Best regards,

Getfem-users mailing list

Attachment: ronan_perrussel.vcf
Description: Vcard

reply via email to

[Prev in Thread] Current Thread [Next in Thread]