ElmerPlugin writes out straight from Salome to Elmer format. Currently recognized Elmer element types are:
1-D: 202, 203
2-D: 303, 306, 404, 408, 409
3-D: 504, 510, 605, 613, 706, 715, 808, 820, 827
Others to be added when I need them in my analysis or someone friendly asks.
Node ordering of elements is adjusted according to Elmer node order. Elements are written out to .elements with intermediate comment lines consisting of group names (ElmerGUI has a minor input problem here).
Groups, meshes and submeshes can be exported. I recommend use of groups because the others include lots of unnecessary stuff (lower order elements) which are impossible to get rid of in ElmerGUI. Mesh and submesh possibilities are included for future purposes.
Nodes are written out in Elmer format to .nodes as well with group names as comments lines.
Boundaries are written out in Elmer format, second parent currently always 0 (I need boundaries for loads, constraints and contacts, not for gluing solids together). Boundary element parents are solved on request (some lower order elements can be part of structural mesh) and written to .boundary. Also boundary names are written to .boundary as comment lines.
Mesh, submesh and group names are written to .names.
Overall number of nodes and different element types are written to .header.
The mesh can be read into ElmerGUI as is. ElmerGUI does not recognize the names currently but I made a request for that feature to Elmer team. It would be a big benefit to have descriptive names coming straight from Salome. Also there is an issue of elements getting renumbered in ElmerGUI, that's under discussion now. In Salome I can not help that because typically from large models, some elements are not exported and the numbering is not therefore continuous. Salome renumbers automatically. For efficient and sensible use, element and node numbers should always be the same through the entire chain of tools from meshing to post processing. Let's see what Elmerteam manages to do.
I am testing the code heavily now in real cases, chewing my fingernails and removing bugs. I will publish my code soon, lets see where it can be easily done.
Next step is to add some very often used things like material input to Salome feature tree when I get mad in adding them manually.
- Groups picked for ElmerPlugin export.
- image005.jpg (38.87 KiB) Viewed 1756 times
- Possible boundaries parent's solved.
- image007.jpg (15 KiB) Viewed 1756 times