Troubleshooting Legacy Models
-----------------------------

1.  The search tolerance for Sierra/SD Tied Data must be set carefully
    to ensure that the same nodes that are in contact as in Sierra/SM.

    1.  Use very small search tolerance, in the range of one to two
        orders of magnitude smaller than the capture tolerance in
        Sierra/SM should be sufficient.

    2.  Ideally, nodal contact information should be passed directly
        from Sierra/SM to Sierra/SD (not currently available).

2.  The sidesets used to define the tied contacts in Sierra/SD must be
    defined in the input Exodus file used by Sierra/SM, even if they are
    not used in Sierra/SM.

3.  The material properties for each element are not passed from
    Sierra/SM to Sierra/SD. This is important with nonlinear models.

.. only:: goodyear

  Modifications for modal analysis following SST analysis
  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  When Sierra/SM is used for an SST analysis, the same procedure for
  computing modes in Sierra/SD can be followed, with minor modifications.

  For each block, specify a `rotational_type` `Eulerian` if it is rotating
  in an Eulerian framework. Otherwise, the `rotational_type` is `none`.
  Blocks on the rotating body use `Eulerian`, whereas stationary blocks
  use `none`. An example is given below.

  .. input::
      BLOCK 1
        material 1
        hex8u
        sd_factor=1
        rotational_type Eulerian
      END

  The rotational speed of the rotating body is specified in the `loads`
  section. This speed is specified as a vector with three components, each
  one giving the rotational speed about the corresponding global
  coordinate axis. An example is given below

  .. input::
      LOADS
        body
          rotation = 0 2.95 0
      END

  For SST analysis, a torque is typically specified in Eagle, and a
  corresponding rotational velocity is computed. Since this speed is not
  known beforehand, it must be output from the Eagle run as a global
  variable. Then, that variable can be input into Sierra/SD. The following
  output section will write the steady-state rotational velocity to a
  global variable called `sstrvel`.

  .. input::
      BEGIN RESULTS OUTPUT output_1
        database name = model.e
        database type = exodusII
        component separator character = ""
        at step 0 increment = 1
        global variables  = TOTAL_ITER AS I_TOTAL
        global variables = sstrvel_1 as sstrvel
      END RESULTS OUTPUT output_1

  Once `sstrvel` is known, it can then be copied to the Sierra/SD input
  deck.

  The projection method to approximate the eigenvalues of rolling bodies.
  The syntax for this in the `solution` section is given below.

  .. input::
      SOLUTION
        solver=gdsw
        case one
          receive_sierra_data
            lumped
        case two
          qevp
          method=projection_eigen
          lumped
          nmodes=20
          shift = -100.0
      END
