Yes, that sounds right - here they mean boundary subdomain, so you should only need the mesh and the *_facet_region.xml file to produce the same result with a MeshFunction.In 3D, GMSH has the terms Physical Surface and Physical Volume which distinguish between labels for facet subdomains and volumetric subdomains, respectively. a (piecewise-2D) subdomain of the boundary. Perhaps "subdomain" is confusing, as, in 3D, it can be either a (volumetric) subdomain of the whole simulation domain, or a boundary subdomain, i.e.I think so - it's been a while since I looked through dolfin-convert code, but that is the behaviour I would expect (but any devs may want to correct me!). Is that the reason I didn't get a physical.xml? I did what you said and I saw only 1 volume. I have 6 physical surfaces and 1 physical volume. xml and facet file and use the gmsh tags to represent the left and right surfaces (as in the above eg.)? So, when I import my cube from gmsh to fenics, should I just import main. left, right = compile_subdomains() < DOLFIN_EPS) & on_boundary", They create a 3D cube mesh in Fenics and classify its boundary at opposite ends (x=0 & x=1) as left and right 'subdomains' through the following statement. So, I have a question about usage of the term 'subdomain'.Īre subdomains representation of only 3D volume partitions or can they be used to represent a 2D surface/ boundary too? Is that the reason I didn't get a physical.xml? Will my 6 physical surfaces not classify as subdomains or will they be only called boundaries?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |