I started with PPM right now and I am slowly getting used to it. I have imported a mesh file from Salome in .unv format. In Salome I revolved a 2d surface mesh by 360° and then merged the bordering nodes in Salome. While importing the mesh in PPM this knowlegde of the merged nodes is somehow lost even tough PPM shows the Salome node set of the merged nodes. Is there a workaround to ensure a closed contour or merge the node set in PPM? I mean the geometry itself is closed therefore I can’t use a Tie constraints. Do you have general hints for importing Salome mesh files? I already recognized that pyramid elements have to be avoided in all manners. Do you have some advices for importing mesh files to ensure a compareable “Part” body like in ANSYS where lets say 3 parts build a compound and the mesh borders are closed naturally.
PrePoMax also supports hex mesh creation by revolution thanks to Gmsh implementation. It can’t be revolved by 360° but you can have two halves and then connect them with tie constraints.
Gmsh also has the Coherence Mesh command to merge nodes but it’s not available in PrePoMax.
this can be similar in feature requested below, currently there’s work around using external pre-post CGX by merging. However, another option to connect coincident nodes by equation has been proposed and may be available in the future of PrePoMax.
Ok, I see. For me, this is strange. If nodes are merged in Salome, they should also be exported as such. PrePoMax makes no changes to the mesh when the mesh is imported.
But I see Merge coincident nodes feature is really needed.
Ok so just for your information. In general it seems like Matej mentioned that merge history of nodes is imported. I made a simple testmodel with a 2d surface created in shaper module, then meshed and 360° revolved with merging, imported and solved in PPM (model under internal pressure) without any problems. Therefore my error is somewhere else to find. I will keep you updated.
