Closed sharanroongta closed 12 months ago
Thanks @sharanroongta. This should now be fixed.
Super! Thanks @rquey There is another fix that is required, which is enquoting the string name in the $PhysicalName section.,, i.e.,
$PhysicalNames
1
0 1 "ver0"
$EndPhysicalNames
The current implementation has :
$PhysicalNames
1
0 1 ver0
$EndPhysicalNames
This is the reason to lose the $PhysicalName information after loading the neper generated msh file in gmsh. Please see the issue https://gitlab.onelab.info/gmsh/gmsh/-/issues/2724#note_21790, and the subsequent discussion.
If you agree, I can create a new pull request for the same.
Thanks, Sharan
Yes, if you can, please make the necessary changes and create a pull request (https://neper.info/workflow.html#being-a-contributor).
Describe the bug
After generating a mesh from a tesselation, the msh4 file created does not indicate the physical tags in the $Entities section. As far as my understanding, the tag associated in the $PhysicalNames section should be indicated in the $Entities section too.
To Reproduce
Ran the following commands:
The $ Entities section look like:
The number of physical tags indicated is to be 0. However, the tags generated in the $PhysicalNames section should be reflected here?
If one creates a physical tag using an integer or a string, should be reflected in the $Entities section. For example:
Physical Surface{1} = {1}; Physical Surface{"x0"} = {1};
would generate 2 physical tags.Physical Surface{"x0"} = {1};
would generate 1 physical tagPlease correct me if I am wrong, but this what I observed using
.geo and gmsh
.Thanks again, Sharan Roongta