-----Ursprüngliche Nachricht----- Von: Buesing, Henrik Gesendet: 18 December 2015 13:03 An: 'firedrake@imperial.ac.uk' Betreff: AW: [firedrake] gmsh: Accessing PhysicalNames for boundary conditions
-----Ursprüngliche Nachricht----- Von: firedrake-bounces@imperial.ac.uk [mailto:firedrake- bounces@imperial.ac.uk] Im Auftrag von Stephan Kramer Gesendet: 18 December 2015 12:19 An: firedrake@imperial.ac.uk Betreff: Re: [firedrake] gmsh: Accessing PhysicalNames for boundary conditions
On 18/12/15 11:00, Buesing, Henrik wrote:
On 18 Dec 2015, at 10:52, Buesing, Henrik <HBuesing@eonerc.rwth- aachen.de> wrote:
Dear Justin! Dear Lawrence!
So just to be clear... Firedrake reads in the *.msh as well as the *.geo file. So both have to be present? Only the *.msh file is not sufficient?
Oh no, firedrake doesn't touch the geo file. You should only need the msh file.
But going with your example tests/regression/annulus.msh. In the msh file there is no definition of the Physical Line. This is only present in the *.geo file... So how does firedrake know about "9" as index to the boundary?
The physical ids *are* present in the .msh file. The 'elements' list at the end contains both triangles and line segments. In fact the first 16 are the line segments with the physical id 9, in the 3rd column, and its 2 node numbers in the last 2 columns. The rest are the triangles with a physical id of 10 in the 3rd column, and its 3 nodes in the last 3 columns. See the link that Lawrence gave to see what the other columns indicate [Buesing, Henrik] I guess my problem comes when creating the *.msh file with the gmsh gui. In my test.geo file I have the "Physical Line", but in my test.msh file every element has id "0". Probably I'm doing sth. wrong when creating the files with the gui. Thank you Stephan for clearing this up.