![]() So, based on that, I would stop at properly assigning physical group tags and numbers and do the material properties assignment on the side of your FEM solver. try using postprocessing-intent ElementData, but that renders the use of Physical Group tags useless (as you'll have to do it based on individual element IDs).Since sections with unknown headers are ignored, you can manually (after *.msh is generated) add your data there and provide your solver with the required input functionality based on your needs.You are left with two bad choices (the ones that I can come up with): So, there is not a section that will naturally fit your needs. NodeData, ElementData, ElementNodeData - postprocessing-intent datasets.Entities, Partitioned Entities, Nodes, Elements, GhostElements – geometry definitions.PhysicalNames - the connection between physical groups numbers and names.In v4 (v2 offers even less), the following sections are available (some, optional): (As GMSH just recently updated to v4, we can also look at the previous legacy MSH v2). Thus, we can use the specification of GMSH *.msh. I guess, the intention is to use *.msh file (obtained by GMSH processing the corresponding *.geo file) as an input to the FEM solver. This job is best left to the solver, GMSH provides a simple mechanism to tag groups of elements stl-files I can't do it manually with the gui. Since I have to do this process for multiple hundreds of. In short, you should not (look at question 13 in this section of GMSH FAQ). When I do it manually in gmsh Modules->Geometry->Elementary entities->Add->Volume->klick on the surface-mesh->pressing 'e'->pressing 'q') that works very well.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |