# HMMOVE

Change the input component of an element.

The HMMOVE comment helps to preserve the original user organization of elements into components when exporting and importing models via solver decks. This comment is required when the solver does not have a card/keyword corresponding to the HyperMesh component. In the case of PAM-CRASH, HMMOVE is also used to organize systems into system collectors.

The format of the HMMOVE comment varies with the different solver interfaces.
OptiStruct/Nastran
$HMMOVE comp_id$           eid1    eid2     ...
$rangeid1THRU rangeid2 ... The component ID on the$HMMOVE comment line starts at column 9, and is written using a field width of 8.
The first element ID on each following line starts at column 9, and every element ID is written using a field width of 8.
A continuous sequence of element IDs is written as a range as shown in the third line. The THRU statement is also written using a field width of 8.
A single $HMMOVE comment can consist of either just individual IDs, just ranges, or any combination. A new comment line begins once column 80 is reached. Example: $HMMOVE        8
$50000 50002 50004 50006 50008 50010 50012 50014 50016$          50018THRU       50022
PAM-CRASH
$HMMOVE collector_id Solver card corresponding to 0-D/1-D element or system The collector ID on the$HMMOVE comment line starts at column 9, and its field width that is exactly equal to the number of digits used for the ID.
Examples:
$HMMOVE 9 RBODY / 47283 0 12705 0 0.0 $HMMOVE  1
FRAME /        1       0       0
##HMMOVE elements eid comp_id
Solver card corresponding to 0-D/1-D element
The element ID (eid) on the ##HMMOVE comment line starts at column 19. Both eid and comp_id occupy a field width that is exactly equal to the number of digits used for the corresponding ID, and are separated by a single space.
Example:
\$HMMOVE 9
##HMMOVE elements 2 8
/RBODY/2
26683                                                           2

HMMOVE ?options?

N/A

OptiStruct