<!DOCTYPE html
  PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">

<!--
Copyright (c) 2006 UGS Corp.

All Rights Reserved.

This software and related documentation are proprietary to UGS Corp.
-->
<html>
   <head>
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
      <title>RECURDYNRFI</title>
      <script language="javaScript">
        abridged="false";
        displayConditions=new Array();
      </script>
      <link type="text/css" href="../css/main_styles.css" rel="stylesheet">
   </head>
   <body class="bodydocs" onload="top.pageLoader()" bgcolor="#FFFFFF">
      <hr noshade="true">
      <div class="title_refTopic" id="xps10_pagetitle">RECURDYNRFI </div>
      <hr noshade="true">
      <h4 class="refClassification">Generates RecurDyn Flex Input File </h4>
      <p class="para_refTopic">Generates a RecurDyn Flex Input (RFI) file during SOL 103.</p>
      <div class="title_refCategory">Format: </div>
      <div class="refCategoryContent">
         <p align="center"><img align="bottom" src="graphics/casecontrol4a-recurdynrfi.gif"></p>
      </div>
      <div class="title_refCategory">Examples: </div>
      <div class="refCategoryContent"><pre class="indent">RECURDYNRFI FLEXBODY=YES</pre></div>
      <div class="title_refCategory">Describers:</div>
      <div class="refCategoryContent">
         <table cellpadding="10" cellspacing="" width="100%" align="center">
            <colgroup span="1">
               <col span="1" width="21.48*">
               <col span="1" width="78.52*">
            </colgroup>
            <thead>
               <tr>
                  <th align="left" colspan="1" height="67" rowspan="1">
                     <p class="para_th" align="center"><b class="uiTerm">Describer </b></p>
                  </th>
                  <th align="left" colspan="1" height="67" rowspan="1">
                     <p class="para_th"><b class="uiTerm">Meaning </b></p>
                  </th>
               </tr>
            </thead>
            <tbody>
               <tr>
                  <td align="left" colspan="1" rowspan="1" valign="top">
                     <p class="para_td">FLEXBODY </p>
                  </td>
                  <td align="left" colspan="1" rowspan="1" valign="top">
                     <p class="para_td">Requests the generation of RFI (required). </p>
                  </td>
               </tr>
               <tr>
                  <td align="left" colspan="1" rowspan="1" valign="top">
                     <ul class="unmarkedList">
                        <li>
                           <p class="para_item">NO </p>
                        </li>
                     </ul>
                  </td>
                  <td align="left" colspan="1" rowspan="1" valign="top">
                     <p class="para_td">Standard NX Nastran solution without RFI creation (default). </p>
                  </td>
               </tr>
               <tr>
                  <td align="left" colspan="1" rowspan="1" valign="top">
                     <ul class="unmarkedList">
                        <li>
                           <p class="para_item">YES </p>
                        </li>
                     </ul>
                  </td>
                  <td align="left" colspan="1" rowspan="1" valign="top">
                     <p class="para_td">RFI generation requested. </p>
                  </td>
               </tr>
               <tr>
                  <td align="left" colspan="1" rowspan="1" valign="top">
                     <p class="para_td">FLEXONLY </p>
                  </td>
                  <td align="left" colspan="1" rowspan="1" valign="top">
                     <p class="para_td">Determines if standard DMAP solution and data recovery runs or not after RFI creation is complete.</p>
                  </td>
               </tr>
               <tr>
                  <td colspan="1" rowspan="1" valign="top">
                     <ul class="unmarkedList">
                        <li>
                           <p class="para_item">YES</p>
                        </li>
                     </ul>
                  </td>
                  <td align="left" colspan="1" rowspan="1" valign="top">
                     <p class="para_td">Only RFI creation occurs (default).</p>
                  </td>
               </tr>
               <tr>
                  <td colspan="1" rowspan="1" valign="top">
                     <ul class="unmarkedList">
                        <li>
                           <p class="para_item">NO</p>
                        </li>
                     </ul>
                  </td>
                  <td align="left" colspan="1" rowspan="1" valign="top">
                     <p class="para_td">RFI file creation occurs along with standard DMAP solution and data recovery. </p>
                  </td>
               </tr>
               <tr>
                  <td align="left" colspan="1" rowspan="1" valign="top">
                     <p class="para_td">OUTGSTRS </p>
                  </td>
                  <td align="left" colspan="1" rowspan="1" valign="top">
                     <p class="para_td">Determines if grid point stress is written to RFI. </p>
                  </td>
               </tr>
               <tr>
                  <td colspan="1" rowspan="1" valign="top">
                     <ul class="unmarkedList">
                        <li>
                           <p class="para_item">NO </p>
                        </li>
                     </ul>
                  </td>
                  <td align="left" colspan="1" rowspan="1" valign="top">
                     <p class="para_td">Do not write grid point stress to RFI (default).</p>
                  </td>
               </tr>
               <tr>
                  <td colspan="1" rowspan="1" valign="top">
                     <ul class="unmarkedList">
                        <li>
                           <p class="para_item">YES </p>
                        </li>
                     </ul>
                  </td>
                  <td align="left" colspan="1" rowspan="1" valign="top">
                     <p class="para_td">Write grid point stress to RFI. </p>
                  </td>
               </tr>
               <tr>
                  <td align="left" colspan="1" rowspan="1" valign="top">
                     <p class="para_td">OUTGSTRN </p>
                  </td>
                  <td align="left" colspan="1" rowspan="1" valign="top">
                     <p class="para_td">Determines if grid point strain is written to RFI. </p>
                  </td>
               </tr>
               <tr>
                  <td colspan="1" rowspan="1" valign="top">
                     <ul class="unmarkedList">
                        <li>
                           <p class="para_item">NO </p>
                        </li>
                     </ul>
                  </td>
                  <td align="left" colspan="1" rowspan="1" valign="top">
                     <p class="para_td">Do not write grid point strain to RFI (default). </p>
                  </td>
               </tr>
               <tr>
                  <td colspan="1" rowspan="1" valign="top">
                     <ul class="unmarkedList">
                        <li>
                           <p class="para_item">YES </p>
                        </li>
                     </ul>
                  </td>
                  <td align="left" colspan="1" rowspan="1" valign="top">
                     <p class="para_td">Write grid point strain to RFI. </p>
                  </td>
               </tr>
               <tr>
                  <td align="left" colspan="1" rowspan="1" valign="top">
                     <p class="para_td">MINVAR </p>
                  </td>
                  <td align="left" colspan="1" rowspan="1" valign="top">
                     <p class="para_td">Determines how mass invariants are computed. </p>
                  </td>
               </tr>
               <tr>
                  <td align="left" colspan="1" rowspan="1" valign="top">
                     <ul class="unmarkedList">
                        <li>
                           <p class="para_item">PARTIAL </p>
                        </li>
                     </ul>
                  </td>
                  <td align="left" colspan="1" rowspan="1" valign="top">
                     <p class="para_td">Mass invariants 6 and 8 are not computed. </p>
                  </td>
               </tr>
               <tr>
                  <td align="left" colspan="1" rowspan="1" valign="top">
                     <ul class="unmarkedList">
                        <li>
                           <p class="para_item">CONSTANT </p>
                        </li>
                     </ul>
                  </td>
                  <td align="left" colspan="1" rowspan="1" valign="top">
                     <p class="para_td">Mass invariants 1,2,3 and 9 are computed. </p>
                  </td>
               </tr>
               <tr>
                  <td align="left" colspan="1" rowspan="1" valign="top">
                     <ul class="unmarkedList">
                        <li>
                           <p class="para_item">FULL </p>
                        </li>
                     </ul>
                  </td>
                  <td align="left" colspan="1" rowspan="1" valign="top">
                     <p class="para_td">All nine mass invariants are computed. </p>
                  </td>
               </tr>
               <tr>
                  <td align="left" colspan="1" rowspan="1" valign="top">
                     <ul class="unmarkedList">
                        <li>
                           <p class="para_item">NONE </p>
                        </li>
                     </ul>
                  </td>
                  <td align="left" colspan="1" rowspan="1" valign="top">
                     <p class="para_td">No mass invariants are computed. </p>
                  </td>
               </tr>
               <tr>
                  <td align="left" colspan="1" rowspan="1" valign="top">
                     <p class="para_td">PSETID </p>
                  </td>
                  <td align="left" colspan="1" rowspan="1" valign="top">
                     <p class="para_td">Selects a set of elements defined in the OUTPUT(PLOT) (including PLOTEL) whose connectivity is exported to face geometry into the RFI. (See Remark 16)</p>
                  </td>
               </tr>
               <tr>
                  <td align="left" colspan="1" rowspan="1" valign="top">
                     <ul class="unmarkedList">
                        <li>
                           <p class="para_item">NONE </p>
                        </li>
                     </ul>
                  </td>
                  <td align="left" colspan="1" rowspan="1" valign="top">
                     <p class="para_td">No specific sets are selected, thus all grids, geometry and associated modal data are written to RFI (default). </p>
                  </td>
               </tr>
               <tr>
                  <td align="left" colspan="1" rowspan="1" valign="top">
                     <ul class="unmarkedList">
                        <li>
                           <p class="para_item">setid </p>
                        </li>
                     </ul>
                  </td>
                  <td align="left" colspan="1" rowspan="1" valign="top">
                     <p class="para_td">The connectivity of a specific element set is used to export face geometry.</p>
                  </td>
               </tr>
               <tr>
                  <td align="left" colspan="1" rowspan="1" valign="top">
                     <ul class="unmarkedList">
                        <li>
                           <p class="para_item">ALL </p>
                        </li>
                     </ul>
                  </td>
                  <td align="left" colspan="1" rowspan="1" valign="top">
                     <p class="para_td">The connectivity of all element sets are used to export face geometry. </p>
                  </td>
               </tr>
            </tbody>
         </table><br></div>
      <div class="title_refCategory">Remarks: </div>
      <div class="refCategoryContent">
         <ol type="1" start="1">
            <li>
               <p class="para_item">The creation of the RecurDyn Flex Input file is applicable in a non-restart SOL 103 analysis only.</p>
            </li>
            <li>
               <p class="para_item">The creation of the RecurDyn Flex Input file is initiated by RECURDYNRFI FLEXBODY=YES (other describers are optional) along with the inclusion of the bulk data entry DTI,UNITS. </p>
            </li>
            <li>
               <p class="para_item">The Data Table Input Bulk Data entry DTI,UNITS, which is required for an RECURDYNRFI FLEXBODY=YES run, is used to specify the system of units for the data stored in the RFI (unlike NX Nastran, RecurDyn is not a unitless code). Once identified, the units will apply to all superelements in the model. The complete format is: </p><pre class="indent">DTI     UNITS   1       MASS    FORCE   LENGTH  TIME</pre><p class="para_item">All entries are required. Acceptable character strings are listed below. </p>
               <ul class="unmarkedList">
                  <li>
                     <p class="para_item">Mass: </p>
                     <ul class="unmarkedList">
                        <li>
                           <p class="para_item">KG - kilogram </p>
                           <p class="para_item">LBM &ndash; pound-mass </p>
                           <p class="para_item">SLUG &ndash; slug </p>
                           <p class="para_item">GRAM &ndash; gram </p>
                           <p class="para_item">OZM &ndash; ounce-mass </p>
                           <p class="para_item">KLBM &ndash; kilo pound-mass (1000.lbm) </p>
                           <p class="para_item">MGG &ndash; megagram </p>
                        </li>
                     </ul>
                     <p class="para_item">Force: </p>
                     <ul class="unmarkedList">
                        <li>
                           <p class="para_item">N &ndash; Newton </p>
                           <p class="para_item">LBF &ndash; pound-force </p>
                           <p class="para_item">KGF &ndash; kilograms-force </p>
                           <p class="para_item">OZF &ndash; ounce-force </p>
                           <p class="para_item">DYNE &ndash; dyne </p>
                           <p class="para_item">KN &ndash; kilonewton </p>
                           <p class="para_item">KLBF &ndash; kilo pound-force (1000.lbf) </p>
                           <p class="para_item">MN - millinewton</p>
                        </li>
                     </ul>
                     <p class="para_item">Length: </p>
                     <ul class="unmarkedList">
                        <li>
                           <p class="para_item">KM &ndash; kilometer </p>
                           <p class="para_item">M &ndash; meter </p>
                           <p class="para_item">CM &ndash; centimeter </p>
                           <p class="para_item">MM &ndash; millimeter </p>
                           <p class="para_item">MI &ndash; mile </p>
                           <p class="para_item">FT &ndash; foot </p>
                           <p class="para_item">IN &ndash; inch </p>
                        </li>
                     </ul>
                     <p class="para_item">Time: </p>
                     <ul class="unmarkedList">
                        <li>
                           <p class="para_item">H &ndash; hour </p>
                           <p class="para_item">MIN-minute </p>
                           <p class="para_item">S &ndash; second </p>
                           <p class="para_item">MS &ndash; millisecond </p>
                        </li>
                     </ul>
                  </li>
               </ul>
            </li>
            <li>
               <p class="para_item">Since DTI,UNITS determines all units for the RFI, the units defined in WTMASS, which are important for units consistency in NX Nastran, are ignored in the output to the RFI. For example, if the model mass is kilograms, force in Newtons, length in meters, and time in seconds, then WTMASS would equal 1 ensuring that NX Nastran works with the consistent set of kg, N, and m. The units written to the RFI would be: &ldquo;DTI,UNITS,1,KG,N,M,S&rdquo;. </p>
            </li>
            <li>
               <p class="para_item">You can create flexible body attachment points by defining the component as a superelement or part superelement, in which case the physical external (a-set) grids become the attachment points; or for a residual-only type model, you can use standard NX Nastran ASET Bulk Data entries to define the attachment points.</p>
            </li>
            <li>
               <p class="para_item">The eight mass variants are:</p>
               <p class="para_item"><img align="bottom" src="graphics/casecontrol4a-mass_inv1.gif" border="0"></p>
               <p class="para_item"><img align="bottom" src="graphics/casecontrol4a-mass_inv2.gif" border="0"></p>
               <p class="para_item"><img align="bottom" src="graphics/casecontrol4a-mass_inv3.gif" border="0"></p>
               <p class="para_item"><img align="bottom" src="graphics/casecontrol4a-mass_inv4.gif" border="0"></p>
               <p class="para_item"><img align="bottom" src="graphics/casecontrol4a-mass_inv5.gif" border="0"></p>
               <p class="para_item"><img align="bottom" src="graphics/casecontrol4a-mass_inv6.gif" border="0"></p>
               <p class="para_item"><img align="bottom" src="graphics/casecontrol4a-mass_inv7.gif" border="0"></p>
               <p class="para_item"><img align="bottom" src="graphics/casecontrol4a-mass_inv8.gif" border="0"></p>
               <p class="para_item"><em>s<sub class="subscript">p</sub></em> = [<em>xyz</em>]<em><sup class="superscript">T</sup></em> are the coordinates of grid point p in the basic coordinate system. 
               </p>
               <p class="para_item"><img align="bottom" src="graphics/casecontrol4a-equ10.gif" border="0"></p>
               <p class="para_item">&phi;<em><sub class="subscript">p</sub></em>=partitioned orthogonal modal matrix that corresponds to the translational degrees of freedom of grid <em>p</em>. 
               </p>
               <p class="para_item"><em>I<sub class="subscript">p</sub></em>=inertia tensor <em>p</em>. 
               </p>
               <p class="para_item">&phi;<em><sub class="subscript">p</sub></em><sup class="superscript">*</sup>=partitioned orthogonal modal matrix that corresponds to the rotational degrees of freedom of grid <em>p</em>. 
               </p>
               <p class="para_item"><img align="bottom" src="graphics/casecontrol4a-ufig05.gif" border="0">=skew-symmetric matrix formed for each grid translational degree of freedom for each mode. 
               </p>
               <p class="para_item">M=number of modes. </p>
               <p class="para_item">N=number of grids.</p>
            </li>
            <li>
               <p class="para_item">To accurately capture the mode shapes when supplying SPOINT/QSET combinations, the number of SPOINTS (ns) should be at least ns=n+(6+p), assuming that residual flexibility is on. In the above equation for ns, the number of modes (n) is specified on the EIGR or EIGRL Bulk Data entries; the number of load cases is p. In general, you can&rsquo;t have too many SPOINTs, as excess ones will simply be truncated with no performance penalty. </p>
            </li>
            <li>
               <p class="para_item">For FLEXBODY=YES runs, residual vectors for the component should always be calculated as they result in a more accurate representation of the component shapes at little additional cost. </p>
            </li>
            <li>
               <p class="para_item">OMIT or OMIT1 Bulk Data entries are not supported. </p>
            </li>
            <li>
               <p class="para_item">Lumped mass formulation (default) is required. Either leave PARAM,COUPMASS out of the input file or supply PARAM,COUPMASS,-1 (default) to ensure lumped mass.</p>
            </li>
            <li>
               <p class="para_item">P-elements are not allowed because they are always use a coupled mass formulation. </p>
            </li>
            <li>
               <p class="para_item">PARAM,WTMASS,value with a value other than 1.0 may be used with an NX Nastran run generating an RFI. It must have consistent units with regard to the DTI,UNITS Bulk Data entry. Before generating the RFI, NX Nastran will appropriately scale the WTMASS from the physical mass matrix and mode shapes. </p>
            </li>
            <li>
               <p class="para_item">There is a distinction between how an RECURDYNRFI FLEXBODY=YES run handles element-specific loads (such as a PLOAD4 entry) versus those that are grid-specific (such as a FORCE entry), especially when superelements are used. The superelement sees the total element-specific applied load. For grid-specific loads, the loads attached to an external grid will move downstream with the grid. That is to say, it is part of the boundary and not part of the superelement. This distinction applies to a superelement run and not to a residual-only or parts superelement run. </p>
            </li>
            <li>
               <p class="para_item">The loads specified in NX Nastran generally fall into two categories: non-follower or fixed direction loads (non-circulatory) and follower loads (circulatory). The follower loads are nonconservative in nature. Examples of fixed direction loads are the FORCE entry or a PLOAD4 entry when its direction is specified via direction cosines. Examples of follower loads are the FORCE1 entry or the PLOAD4 entry when used to apply a normal pressure. By default in NX Nastran, the follower loads are always active in SOL 103 and will result in follower stiffness being added to the differential stiffness and elastic stiffness of the structure. In a run with RECURDYNRFI FLEXBODY=YES and superelements, if the follower force is associated with a grid description (such as a FORCE1) and the grid is external to the superelement, the follower load will move downstream with the grid. Thus, the downstream follower contribution to the component&rsquo;s stiffness will be lost, which could yield poor results. This caution only applies to a superelement run and not to a residual-only or a part superelement run. </p>
            </li>
            <li>
               <p class="para_item">OUTGSTRS and OUTGSTRN entries require the use of standard NX Nastran STRESS= or STRAIN= used in conjunction with GPSTRESS= or GPSTRAIN= commands to produce grid point stress or strain. GPSTRESS(PLOT)= or GPSTRAIN(PLOT)= will suppress grid stress or strain print to the NX Nastran .f06 file. </p>
            </li>
            <li>
               <p class="para_item">To reduce the FE mesh detail for dynamic simulations, PSETID (on the RECURDYNRFI Case Control command) defined with a SET entry is used to define a set of PLOTELs or other elements used to select grids to display the components in RecurDyn. This option can significantly reduce the size of the RFI without compromising accuracy in the FunctionBay simulation providing that the mass invariant computation is requested. With superelement analysis, for any of these elements that lie entirely on the superelement boundary (all of the elements&rsquo; grids attached only to a-set or exterior grids), a SEELT Bulk Data entry must be specified to keep that display element with the superelement component. This can also be accomplished using PARAM, AUTOSEEL,YES. The SEELT entry is not required with parts superelements, as boundary elements stay with their component. </p>
               <p class="para_item">If the SET entry points to an existing set from the OUTPUT(PLOT) section, this single set is used explicitly to define elements used to select grids to display the component in RecurDyn. If PSETID does not find the set ID in OUTPUT(PLOT), it will search sets in the case control for a matching set ID. This matching set ID list then represents a list of OUTPUT(PLOT) defined elements&rsquo; sets, the union of which will be used to define a set of PLOTELs or other elements used to select grids to display the component in RecurDyn. If the user wishes to select all of the sets in the OUTPUT(PLOT) section, then use PSETID=ALL. </p>
               <p class="para_item">The following element types are not supported for writing to an RFI, nor are they supported as a &lsquo;type&rsquo; entry in a set definition in OUTPUT(PLOT): CAABSF, CAEROi, CDUMi, CHACAB, CHACBR, CHBDYx, CDAMP3, CDAMP4, CELAS3, CELAS4, CFLUIDi, CMASS3, CMASS4, CRAC2D, CRAC3D, CTRMEM, CTWIST, CWEDGE, CWELD, and GENEL.</p>
            </li>
            <li>
               <p class="para_item">Typical NX Nastran data entry requirements are described below. </p>
               <p class="para_item">Typical Parameters: </p>
               <ul>
                  <li>
                     <p class="para_item">PARAM,RESVEC,character_value &ndash; controls calculation of residual flexibility (including inertia relief) modes. In SOL 103, residual flexibility is on by default for only component modes (o-set). </p>
                  </li>
                  <li>
                     <p class="para_item">PARAM,GRDPNT,value - mass invariants <sup class="superscript">1</sup><em>I</em>, <sup class="superscript">2</sup><em>I</em>, and <sup class="superscript">3</sup><em>I</em> will be computed using results of NX Nastran grid point weight generator execution in the basic coordinate system. 
                     </p>
                  </li>
               </ul>
               <p class="para_item">Typical Case Control: </p>
               <ul>
                  <li>
                     <p class="para_item">RECURDYNRFI FLEXBODY=YES is required for RFI generation.</p>
                  </li>
                  <li>
                     <p class="para_item">METHOD=n is required before or in the first subcase for modal solutions. </p>
                  </li>
                  <li>
                     <p class="para_item">SUPORT1=seid is necessary to select a static support set for a residual only linear preload run.</p>
                  </li>
                  <li>
                     <p class="para_item">SUPER=n,SEALL=n is useful with multiple superelement models to select an individual superelement as a flexible body. Cannot be used with a linear STATSUB(PRELOAD) run. </p>
                  </li>
                  <li>
                     <p class="para_item">OUTPUT(PLOT) is necessary to define elements used to select grids to display the component in RecurDyn when PSETID=ALL or setid. </p>
                     <p class="para_item">SET n=list of elements (including PLOTELs) is used to select grids to display the component. </p>
                  </li>
                  <li>
                     <p class="para_item">OUTPUT(POST) is necessary to define volume and surface for grid stress or strain shapes. </p>
                     <p class="para_item">SET n=list is a list of elements for surface definition for grid stress or strain shapes. </p>
                     <p class="para_item">Stress and strain data in the RFI is limited to the six components (i.e. 3 normal and 3 shear) for a grid point for a given mode. </p>
                     <p class="para_item">SURFACE n SET n NORMAL z3 is used to define a surface for writing stress and strain data. Only one FIBER selection is allowed for each SURFACE, thus the use of the FIBRE ALL keyword on the SURFACE case control command will write stresses to the RFI at the Z1 fiber location only. </p>
                     <p class="para_item">Since the FIBRE keyword only applies to stresses, strain data will always be written to the RFI at the MID location. </p>
                     <p class="para_item">Stress and strain data at grid points can only be written to the RFI for surface and volume type elements (e.g. CQUAD and CHEXA). </p>
                     <p class="para_item">VOLUME n SET n is a volume definition. </p>
                     <p class="para_item">The default SYSTEM BASIC is required with SURFACE or VOLUME. </p>
                  </li>
                  <li>
                     <p class="para_item">STRESS(PLOT) is necessary for stress shapes. </p>
                  </li>
                  <li>
                     <p class="para_item">STRAIN(PLOT) is necessary for strain shapes. </p>
                  </li>
                  <li>
                     <p class="para_item">GPSTRESS(PLOT) is necessary for grid point stress shapes to be included in the RFI. </p>
                  </li>
                  <li>
                     <p class="para_item">GPSTRAIN(PLOT) is necessary for grid point strain shapes to be included in the RFI. </p>
                     <p class="para_item">Typical Bulk Data: </p>
                  </li>
                  <li>
                     <p class="para_item">DTI,UNITS,1,MASS,FORCE,LENGTH,TIME is required for RFI generation. For input files containing superelements, this command must reside in the main bulk data section. </p>
                  </li>
                  <li>
                     <p class="para_item">SPOINT,id_list defines and displays modal amplitude.</p>
                  </li>
                  <li>
                     <p class="para_item">SESET,SEID,grid_list defines a superelement (see GRID and BEGIN BULK SUPER=). The exterior grids will represent the attachment points along with the q-set.  </p>
                  </li>
                  <li>
                     <p class="para_item">SEELT,SEID,element_list reassigns superelement boundary elements to an upstream superelement. </p>
                  </li>
                  <li>
                     <p class="para_item">RELEASE,SEID,C,Gi is an optional entry that removes DOFs from an attachment grid for which no constraint mode is desired. For example, this allows the removal of rotational degrees of freedom from an analysis where only translational degrees of freedom are required. </p>
                  </li>
                  <li>
                     <p class="para_item">SEQSET,SEID,spoint_list defines modal amplitudes of a superelement (see SEQSET1). </p>
                  </li>
                  <li>
                     <p class="para_item">SENQSET,SEID,N defines modal amplitudes of a part superelement. It must reside in the main Bulk Data Section. </p>
                  </li>
                  <li>
                     <p class="para_item">ASET,IDi,Ci defines attachment points for a residual-only run (see ASET1). </p>
                  </li>
                  <li>
                     <p class="para_item">QSET1,C,IDi defines modal amplitudes for the residual structure or modal amplitudes for a part superelement (see QSET). </p>
                  </li>
                  <li>
                     <p class="para_item">SUPORT1,SID,IDi,Ci defines the static support for a preload condition with a residual-only run. This entry is case control selectable. Do not use SUPORT. </p>
                  </li>
                  <li>
                     <p class="para_item">PLOTEL,EID,Gi can be used, along with existing model elements, to define elements used to select grids to display the components in RecurDyn. </p>
                  </li>
                  <li>
                     <p class="para_item">EIGR,SID,METHOD,&hellip; obtains real eigenvalue extraction (see EIGRL).</p>
                  </li>
               </ul>
            </li>
            <li>
               <p class="para_item">RECURDYNRFI and ADAMSMNF case control entries cannot be used in the same analysis run. In other words, a RecurDyn RFI file or an ADAMS MNF file can be generated during a particular NX Nastran execution, but not both files at the same time. Attempting to generate both files in the same analysis will cause an error to be issued and the execution to be terminated.</p>
            </li>
         </ol>
      </div>
   </body>
</html>