RELOC

Each transformation can be defined by a combination of GRID points and numeric values (real numbers) representing distances and angles. The grid ID fields can be input as either numeric (positive integer) or fully qualified references to grid points in the model. Numeric references (without part name) specify grid points in the global part.

Format

Translation (TYPE = MOVE) Format 1

Format 2

Rotation (TYPE = ROTATE) Format 1

Format 2 (axis + angle)

Format 3 (axis + angle defined by grids)

Format 4 (2D, grid + angle defined by grids)

Matching (TYPE = MATCH) Format 1

Format 2 (2D)

Mirroring (TYPE = MIRROR) Format 1

Format 2 (match + mirror)

Format 3 (2D mirroring)

Format 4 (2D, matching + mirroring)

Example

Definitions

Comments

1. A RELOC entry can be referenced by a INSTNCE entry to define the location of a part in the full model. Additionally, the PERBC entry references the RELOC entry to define geometric relationship between two sets of boundary grid points.
2. The following illustrations depict part relocation examples for each of the four TYPE field options. All grid point ID's used on the RELOC entry can belong to any part in the model. Only their initial locations are relevant. All RELOC entries are evaluated before any parts are moved. This may not always produce the expected result in some cases as the sequence of moves affects the final part locations. For example, if RELOC, MATCH is defined using three grid points on part A and three grid points in part B, this may not result in a final structure with the two parts being connected, if part B is moved again after this matching process. To avoid such cases, it is strongly recommended to assign the grid points that define the initial location to a part that has to be moved and the grid points that define the final location, to a part that will not be moved (for example, the global structure).

   
   
   Figure 1. Translation - Format 1

   
   
   Figure 2. Format 1 (Special case, assumes that Part B does not relocate)

   
   
   Figure 3. Translation - Format 2

   (1)
   $$D=\sqrt{{\left(dx\right)}^2+{\left(dy\right)}^2+{\left(dz\right)}^2}$$
   Where, D is the distance moved by the part referenced on the INSTNCE entry, and dx, dy and dz are the distances moved by the part along the X, Y and Z axes.

   
   
   Figure 4. Rotation - Format 1

   
   
   Figure 5. Matching - Format 1

   
   
   Figure 6. Format 1 (Special case - Part B does not relocate)

   
   
   Figure 7. Mirroring - Format 1

3. In a 2D model, only two TYPE options are allowed: ROTATE and MIRROR. All grid points in the model should have the same Z coordinate. Rotation and mirroring are defined in the X-Y plane.

   Table 1. Rotation in a 2D Model Defined in the X-Y Plane

   (1)	(2)	(3)	(4)	(5)	(6)	(7)	(8)	(9)	(10)
   RELOC	ID	ROTATE	GID1			ang_z

   Table 2. Mirroring in a 2D Model Defined in the X-Y Plane

   (1)	(2)	(3)	(4)	(5)	(6)	(7)	(8)	(9)	(10)
   RELOC	ID	MIRROR	GIDA1	GIDA2

4. In special cases where a model is defined in the X-Y plane (or a plane parallel to the X-Y plane), all RELOC type options (MOVE, MATCH, ROTATE and MIRROR) are supported to relocate the part in the same plane in the same way as a 2 dimensional transformation. In such cases, simplified card formats are implemented to provide easier specifications of relocation.
   Note: All grid points in the model should have the same Z coordinate. Rotation and mirroring are defined in the X-Y plane.
5. Supported local entries in specific parts can be referenced by the use of "fully-qualified references" on RELOC entries in the model. A fully-qualified reference (PartName.number) is similar to the format of a numeric reference. PartName is the name of the part that contains the referenced local entry (part names are defined on the BEGIN Bulk Data Entry in the model). number is the identification number of a referenced local entry in the part PartName. See Parts and Instances in the User Guide for detailed information on the use of fully-qualified references.
6. Relocation is computed internally using initial locations of all GRIDs specified on the corresponding RELOC entry. It is not affected by any movement of parts due to the INSTNCE entry. For example, the entry RELOC, 5, aaa.1, bbb.2 does not indicate that parts aaa and bbb will be connected together after all the INSTNCE cards are processed.
7. For RELOC entries using GRID match (MATCH formats 1,2 and MIRROR formats 2,4), the starting configuration should match the ending configuration. That is, the distances between matched GRID's should be the same prior to and after relocation (for example, GIDA1, GIDA2 to GIDB1, GIDB2).