#1080: HM Connector Imprint (11.0.

101)
Product: HyperMesh
Product Version: HW-11.0-101 and above
Computer Operating System:
Windows: x86_32, x86_64.
Linux RHEL 5.4& SLED11: x86_32, x84_64
Mac OS x 10.6: x85_64

Topic Objective:
Use mesh imprint to prevent conflicting transitions during connector realization

Topic Details:
When creating mesh-dependent realizations with quad transitions, the quad transition meshes can
overlap and disturb each other if more than one set of connectors is created too close to each other.
The connector imprint panel provides a way to reconcile such transitions with each other and then
modify the underlying mesh to match the results. This creates a seamless, properly meshed final result.
Different Use cases: In the picture below, the regular quad mesh can be easily performed. There is
enough space available and the quad transition areas dont conflict each other.

2013 Altair, Proprietary and Confidential

Pg 1

However, when the components are brought closer together, the realization fails because the transition
areas conflict with each other.

Smaller conflicts can be resolved automatically by the resolve conflicting imprints option when realizing
the connectors. This releases the overlapping elements and performs a normal remesh in that area. This
is permitted as long as the overlapping area is smaller than half the regular quad transition element size.

However, if a conflict is too great it cannot be resolved in this fashion. For such cases, the mesh edit imprint functionality can be used to solve the problem.

2013 Altair, Proprietary and Confidential

Pg 2

The Solution: Manual Mesh Imprint

Ideally all connectors expected to conflict with each other are realized with the skip imprint option in a
first step. This creates the weld elements and the mesh pattern for each connector. The pattern elements
are organized into a component named ^conn_imprint.

In a third step the manual mesh imprint is performed. The elements from the ^conn_imprint component
are selected as the source and the elements from the affected components are selected
as destination mesh.
The mesh edit imprint functionality can be used in various situations, but when using it together with
connectors certain rules should be taken into account. The imprint mesh (source) should not cross the
borders of the destination mesh or component, whether at a free edge or at a changeover to another
component. Furthermore, the imprint mesh should not exceed a certain distance from the destination
mesh. You can limit this by activating the check max distance checkbox.
Note: Only when these requirements are met can reliable results can be expected.

2013 Altair, Proprietary and Confidential

Pg 3

By activating the checkbox elems to destination comp the elements from

the ^conn_imprint components are automatically organized into the appropriate destination
components:

2013 Altair, Proprietary and Confidential

Pg 4

Panel Usage
The panel includes collectors for specifying the imprint mesh (source) and the destination mesh, as well
as an option to determine which components the imprint will be organized into. There are additional
settings to be made; for further details see the mesh edit panel
This screenshot displays the recommended panel settings for mesh imprint in combination with
connectors:

Panel Input:
Source: The elements selected in this field will be imprinted into the destination mesh when the imprint is
performed.
Destination: The elements which are intended to assimilate the imprint mesh are selected in this field.
Elems to destination comp: This checkbox determines whether the imprint elements should remain in
their origin component or be organized into the appropriate components of the destination mesh.
Create: Applies the imprint based on the provided input.
Reject: Reverses the last imprint action.
Note that the imprint is finalized if you leave the panel, so you cannot reject it if you leave the panel and
then return again.
Return: Exits the connector imprint panel.
The current state of the imprint is saved, but the entry option settings are not saved

2013 Altair, Proprietary and Confidential

Pg 5