[baloe]

Hello,
I have an axisymmetric problem which I am solving in Fluent.
It appeared straight forward to me to create a 2D mesh in ICEM which I have been using for preliminary planar studies.
My mostly structured 2D mesh contains multiple face zones separated and/or limited by 1D parts all of which are named.

Now I would like to extrude the 2D mesh (mesh.uns, *.msh, etc) to carry out 3D calculations. Upon doing so I want

• the names of my old 2D faces to be transferred to the newly created 3D volumes
• the names of my old 1D boundaries to be transferred to the newly created 2D faces that now separate and/or limit the volumes
• the old plane to be assigned a new name (it would now be a periodic boundary, a wall or a symmetry plane)
• the new plane to be assigned a separate name (same here)

but this appears to be just about impossible to do using ICEM:

• upon extruding 2D faces all the created perpendicular faces are assigned a single part name
• Upon extruding 1D line elements I get the 2D faces separating my 3D volumes and being named correctly, but then the mesh is faulty, because the above created volumes and the here created faces coexist without being connected

Any advise would be greatly appreciated, also on alternative meshing tools.
Thank you

Update 1
This is pretty much the same question and an answer mentions bar elements. Will look into it tomorrow: ICEM CFD 5.0 - 2D to 3D Mesh Extrude

Update 2
Ok, so the extrusion actually works as expected when I set new side parts and volume to inherited except that the 2D faces in the original plane need to be assigned a new part manually which is ok though for they will all go into the same part and can be selected by geometry easily.

The generated *.msh mesh file becomes corrupted though - I can load it into fluent, but a mesh check reveals number of errors

If I save the mesh as an *.cfx5 file, load it into cfx5pre, then write a *.def definition file and load this definition file into fluent, the mesh check succeeds.
This is a really cumbersome procedure.

Update 3
Turned out, the names I had given some of the interior surfaces in ICEM were to blame and corresponding surfaces were loaded as interfaces which raised the mesh check error.
So I have my ICEM script rename all those surfaces appropriately before exporting to *.msh and all should be fine