Hi,
I think I got it now. The numbers after dimension for the line entity inside Periodic are the matching tag entities for the lines. I was getting confused as I kept looking at line labels.

Thanks again
Ranga Sudarsan

On 27/04/2017 7:20 AM, DILASSER Guillaume wrote:

Hi,

Have you looked at the documentation here <http://gmsh.info/doc/texinfo/gmsh.html#MSH-ASCII-file-format> ? It says :

/$Periodic/

/number-of-periodic-entities/

/dimension slave-entity-tag master-entity-tag/

/number-of-nodes/

/slave-node-number master-node-number/

/…/

/$EndPeriodic/

It looks like your information.

Faithfully Yours,

Guillaume DILASSER

Doctorant SACM / LEAS

CEA - Centre de Saclay - Bât.123 - PC 319c

91191 Gif sur Yvette Cedex - France -

[email protected] <mailto:[email protected]>

*De :*gmsh [mailto:[email protected]] *De la part de* Ranga Sudarsan
*Envoyé :* jeudi 27 avril 2017 12:56
*À :* gmsh mailing list <[email protected]>
*Objet :* [Gmsh] Help understanding MSH file entries while using "Periodic surface with translate "

Hi there,
I am meshing a geometry with periodic (translated meshes) boundary conditions along one of the directions (X in my case). I am using periodic surface with translate to setup the translated periodic meshes. I need help understanding some entries in the Msh file generated specifically the section under "$Periodic" (See attached image, in my case surfaces 1 and 8 are periodic). I understand that in my case their are totally 11 periodic entities -- 5 points , 5 lines and 1 surface and my trouble is in understanding the format of the output corresponding to each of these periodic entities. It will be of great help if some one explain to me what is the format for each of these entities so that I can write a code to read the msh file and generate relevant input files for my finite element solver. I have attached the geo and mesh file.

Thanks again
Ranga Sudarsan


_______________________________________________
gmsh mailing list
[email protected]
http://onelab.info/mailman/listinfo/gmsh

Reply via email to