7.4.3. Subdomains and Boundary Sets

HYPERMESH does not understand the concept of subdomains or boundaries of Ansys Polyflow. So, in HYPERMESH you have to specify the components. Each component is a tag (name) and contains a set of elements. The translator will not allow you to mix elements of different dimensions, example, triangle and hexagons, in the same component.

  • For 2D meshes, components constituted with segments (bar2, in the naming of HYPERMESH) will be considered as boundaries, while components constituted with triangles and quads (tri3 and quad4 in the naming of HYPERMESH) will be considered as subdomains.

  • For 3D meshes, components constituted with triangles and quads (tri3 and quad4, in the naming of HYPERMESH) will be considered as boundaries, while components constituted with tets, wedges, pyramids and hexs (tetra4, pyramid5, penta6 and hexa8 in the naming of HYPERMESH) will be considered as subdomains.

It is not allowed to have elements owned by two components, or to define internal boundaries. The names given in HYPERMESH will be replaced during conversion by a subdomain id or boundary id, in the order with which you find the components in the file. The subdomain and boundary numbering will be reported by Ansys Polydata after the conversion is complete. For more information about creating components, refer to HYPERMESH user’s manual.