[ICEM] Export changes part names

eknight · March 13, 2019, 10:27

Hi everyone,

My project has a lot of parts and the naming convention is important to conserve while using it in Fluent. Currently, I am trying to export my mesh into a .msh file, but whenever I do the prefix "int_" gets added to all my parts that are set as interiors in my boundary conditions.

Is there any way to stop this?

Many thanks

bluebase · March 14, 2019, 05:44

Hi Eknight,

i don't know a way to stop this...

However, i guess there is a workaround. Open your .msh file in a text-editor. At the end of the file, there is line (0 "Zone Sections"). Below that, you find the boundary conditions and their names.Here you could fix the interior names.
Replacing all "interior int_" with "interior " in the .msh could be a simple solution (mind the spaces). It should work in binary and ascii format if you only replace below the zone sections line.

Best regards,
Sebastian

March 13, 2019, 10:27	Export changes part names	#1
eknight New Member Join Date: Jan 2019 Posts: 3 Rep Power: 7	Hi everyone, My project has a lot of parts and the naming convention is important to conserve while using it in Fluent. Currently, I am trying to export my mesh into a .msh file, but whenever I do the prefix "int_" gets added to all my parts that are set as interiors in my boundary conditions. Is there any way to stop this? Many thanks

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
[ICEM] Extrude 2D mesh, face names to volume names, line names to face names	baloe	ANSYS Meshing & Geometry	0	January 6, 2017 17:39
Naming export files in Workbench scripts	evan247	CFX	1	January 22, 2015 20:23
[snappyHexMesh] crash sHM	H25E	OpenFOAM Meshing & Mesh Conversion	11	November 10, 2014 11:27
Exporting part names to Fluent	morourke	ANSYS Meshing & Geometry	1	February 22, 2010 11:36
OpenFOAM on MinGW crosscompiler hosted on Linux	allenzhao	OpenFOAM Installation	127	January 30, 2009 19:08

March 14, 2019, 05:44		#2
bluebase Senior Member Sebastian Engel Join Date: Jun 2011 Location: Germany Posts: 566 Rep Power: 20	Hi Eknight, i don't know a way to stop this... However, i guess there is a workaround. Open your .msh file in a text-editor. At the end of the file, there is line (0 "Zone Sections"). Below that, you find the boundary conditions and their names.Here you could fix the interior names. Replacing all "interior int_" with "interior " in the .msh could be a simple solution (mind the spaces). It should work in binary and ascii format if you only replace below the zone sections line. Best regards, Sebastian