[Q] I have created mesh in two separate project using blocking technique? I am unable to merge the two set of data?

[A] Ansys Recommended solution is described in this hyperlink.
[Q] I am using patch-dependent surface meshing in ICEM and the mesh quality on individual surface is good. However, the line elements the the common edge of two surfaces are overlapping though the number of elements on that edge is set to be same!

[A] Check and toggle on the checkbox "Respect Line Elements" under Global Mesh Setup --> Surface Mesh.
Respect Line Elements
[Q] I have created a cross-section of axi-symmetric model using points, curves and arcs. However, ICEM CFD is unable to create a surface from lines. Even, "Close Hole" option under "Repair Geometry" tab failed!

[A] There are two ways to resolve this issue:
  1. Segregate the curves in a set of 3 curves so that ICEM is able to create a surface. Use 4th edge of the curves created this way with adjacent curves to create another surface on so on. This way you will get a patch of surfaces which can be easily meshed with either "All Quad" or "Quad Dominant" option.
  2. In case you are interested in only one surface whose edge is defined by the envelope you created, make a rectangular surface which encompass all the curves and points defining cross-section of the domain. Trim this surface using closed-loop of the curves. In my experience, ICEM has never failed to trim the surface for a loop comprising of up to 40 curves (straight lines and arcs).
[Q] I have written a long script to create a very complex 2D domain using bottom-up approach. The naming convention used for points is pnt1, pnt2, ..., pnt10, pnt11, ... Some temporary points required to create an arc are center points named as cp. However, the script is generating a point named cp00. When I checked the script, there is no name "cp00" appearing in it.

[A] This might have happen when you would have tried to create a point named "cp" second time without deleting the first one. As per default setting, ICEM does not allow to overwrite an entity name.
[Q] The surfaces in ICEM do not look very smooth. Also, when I extracted an Iso-line, it does not seem to lie in the plane of the surface. Is it an aberration or just a visualization issue?

[A] This is a program setting issue. All the surfaces in CAD environment are represented as what is called Tessellation. Set the triangulation tolerance to an appropriate low value. Read the user manual about "triangulation toleration" and its effect on treatment of geometry in ICEM. See the effect of this tolerance as demonstrated below!
Display Tolerance
Display Tolerance in ICEM CFD Note: STAR CCM+ uses feature angle value to control tessellation densities for import of data in neutral format such as iges, step or parasolid. The angles used are 12, 6, 3, 1.5, 0.75 degrees, moving from coarse to very fine.
[Q] ICEM is not dividing a particular curve as per the number of nodes set explicitly. The mesh is being generated by "Patch-dependent" method.

[A] Check the global mesh setting parameter. Is natural sizing on? What value MIN mesh size to ignore set to? Though mesh sizing on curve takes priority over Global setting, natural sizing is also meant for curves. Hence, check which of the two is the smallest one? The element size after setting number of nodes should be greater than the value set in Global Mesh Sizing Option.
[Q] I have many T-junction in my geometry. How can I generate good quality HEXA mesh.

[A] Using the blocking technique in ICEM CFD and O-grid split, a high quality mesh can be generated for any tye of T-junction or Y-junction. Refer to few examples below.
Hex Mesh Example in ICEM CFD
Hex Mesh Example using BLocking in ICEM CFD
[Q] The transition from a fine mesh to coarse mesh is not consistent and as desired.

[A] A good transition from a fine mesh to coarse mesh requires consistent meshing set-up for all the geometrical entities: points, curves and surfaces. It is advised to keep the lines and points in the parts defining the finer mesh and set meshing parameters using parts option instead of individually on every line and surface (unless there is some specific requirements).

The mesh with not correct transition is shown below. The left curve defining the boundary of smaller patch was kept in the part encircling the patch.
Incorrect Mesh
The mesh with proper transition is shown below. The left curve defining the boundary of smaller patch was moved into the part defining the patch. Correct Mesh
[Q] Fluent automatically assigns interface to zones which are supposed to be interior.

[A] If a part is named with prefix INTERFACE such as INTEFACE_ABC and then exported as fluent format. When it is imported in Fluent (read mesh operation), fluent will automatically assign it the zone type 'interface'. In order to change it to zone type 'interior', first convert it to zone type 'wall' and then to 'interior'. However, once and interface or wall is set to interior, it cannot be directly set to zone type interface using the drop down option (as this option will not be available). The zone type back to interface now be set through 'TUI' only.
  • Use mesh/modify-zones/slit-face-zone: to slit the 'interior' zone which needs to be converted to 'interface'.
  • The above operation will create two zones of type wall, a wall and a shadow-wall
  • The newly created two walls can still be not set to interface
  • Use the same TUI command: mesh/modify-zones/slit-face-zone on the zone type 'wall' created in step-1
  • This operation will now replace the zone types 'wall' and 'shadow-wall' with two new zones named as wall-n and wall-m where 'n' and 'm' are numbers determined by the program
  • Not convert the new zones 'wall-n' and 'wall-m' to type interface using drop-down option.
  • Finally create a conformal interface using standard GUI approach.

The content on is being constantly refined and improvised with on-the-job experience, testing, and training. Examples might be simplified to improve insight into the physics and basic understanding. Linked pages, articles, references, and examples are constantly reviewed to reduce errors, but we cannot warrant full correctness of all content.