FreeCAD|
|
ElmerGui_IMportUNV.png (85,936 bytes) |
|
|
Kdevelop_IMportUNV.png (117,893 bytes) |
|
|
Salome_mesh_preparation_IMportUNV1.png (168,647 bytes) |
|
|
http://docs.salome-platform.org/latest/gui/SMESH/creating_groups_page.html http://www.salome-platform.org/forum/forum_10/982903177 http://www.salome-platform.org/user-section/salome-tutorials/example-of-group |
|
|
Hi wmayer, 0)thanks for dealing with this issue. 1) the second link of the forum shows that there is a confusion about the word "groups" within salome's naming. 2) "Group" can be hold as container saying nothing about its contents. Gmsh has got a name for one content in question: PE: additional "information needed for the solver": a) per element body information (material), b) per node boundary information (such as external temperature) http://forum.freecadweb.org/viewtopic.php?f=18&t=13623 3)imho core is just to figure out where this boundary-body-info goes, to be able to manipulate it (at an UI) before export .unv or the like. 4) Even if the above can be seen as core functionality, having a look at link 3: "Group can be used for definition of boundary conditions, for selection of bad elements. " one sees that the groups(=container) mechanism in salome can be used for other things as well - beyond the core problem. 5) good luck in landing salome mesh to fc! |
|
|
downgraded severity to 'minor' from 'blocker' |
|
|
The unv importer imports the group data and saves it in the FreeCAD FEM mesh structure. By python it can be extracted. The unv exporter exports this group data again to unv. I do not really understand what is this bug report about. May be the problem was at the time when it was reported it was not possible to read the group data from inside FreeCAD. That is why it was spoken about hidden mesh data. From my point the issue could be closed. bernd |
- Anonymous
