[Gmsh] Physical region numbering

[j s]

I was burned by this several years ago.  I guess I have been lucky in
that the numbering stayed unique, but it now looks like ambigious
physical-numbers have come to pass.  Now I have to make sure my solver
supports ambiguous physical-numbers as well.

http://www.mail-archive.com/gmsh@geuz.org/msg01503.html

Thanks for discovering this.



On Mon, Jun 24, 2013 at 5:40 AM, Dharmendar Reddy
<dharmareddy84 at gmail.com> wrote:
> Hello,
>          I am using the gmsh 2.7.1 source code to create a mesh using
> GModel. I find that GModel.witeMSH("fileName") writes a mesh where the
> physical region numbering:
>
>      $PhysicalNames
>      number-of-names
>      physical-dimension physical-number "physical-name"
>      ...
>      $EndPhysicalNames
>
> has a physical-number which starts at 0 for each physical dimension.
>
> When i create the same mesh using gui interface to gmsh (2.4.2 and 2.6.1) i
> get the physicalNames section with continuous numbering for the physical
> regions irrespective of its physical dimension.
>
> Is this an expected behavior ? What should i do to get continuous numbering
> when i created the mesh using gmsh library.  I have mesh reader for gmsh msh
> file which expects a continuous numbering for the regions.
>
> Thanks
> Reddy
>
>
> --
> -----------------------------------------------------
> Dharmendar Reddy Palle
> Graduate Student
> Microelectronics Research center,
> University of Texas at Austin,
> 10100 Burnet Road, Bldg. 160
> MER 2.608F, TX 78758-4445
> e-mail: dharmareddy84 at gmail.com
> Phone: +1-512-350-9082
> United States of America.
> Homepage: https://webspace.utexas.edu/~dpr342
>
> _______________________________________________
> gmsh mailing list
> gmsh at geuz.org
> http://www.geuz.org/mailman/listinfo/gmsh
>