doc/FREQUENCY.html

<html><head><link rel="stylesheet" type="text/css" href="style.css"/></head><body> <H2> <BR> *FREQUENCY </H2>  <P> Keyword type: step  <P> This procedure is used to determine eigenfrequencies and the corresponding eigenmodes of a structure. The frequency range of interest can be specified by entering its lower and upper value. However, internally only as many frequencies are calculated as requested in the first field beneath the *FREQUENCY keyword card. Accordingly, if the highest calculated frequency is smaller than the upper value of the requested frequency range, there is no guarantee that all eigenfrequencies within the requested range were calculated. If the PERTURBATION parameter is used in the *STEP card, the load active in the last *STATIC step, if any, will be taken as preload. Otherwise, no preload will be active.  <P> There are four optional parameters SOLVER, STORAGE, GLOBAL and CYCMPC. SOLVER specifies which solver is used to perform a decomposition of the linear equation system. This decomposition is done only once. It is repeatedly used in the iterative procedure determining the eigenvalues. The following solvers can be selected:  <P>  <UL> <LI>the SGI solver </LI> <LI>PaStiX  </LI> <LI>PARDISO </LI> <LI>SPOOLES [3,4].  </LI> <LI>TAUCS  </LI> <LI>MATRIXSTORAGE. This is not really a solver. Rather, it is an option   allowing the user to store the stiffness and mass matrix. </LI> </UL>  <P> Default is the first solver which has been installed of the following list: SGI, PaStiX, PARDISO, SPOOLES and TAUCS. If none is installed, no eigenvalue analysis can be performed.  <P> The SGI solver should by now be considered as outdated.SPOOLES is very fast, but has no out-of-core capability: the size of systems you can solve is limited by your RAM memory. With 32GB of RAM you can solve up to 1,000,000 equations.  TAUCS is also good, but my experience is limited to the <SPAN CLASS="MATH"><B><IMG  WIDTH="35" HEIGHT="17" ALIGN="BOTTOM" BORDER="0"  SRC="img2241.png"  ALT="$ LL^T$"></B></SPAN> decomposition, which only applies to positive definite systems. It has an out-of-core capability and also offers a <SPAN CLASS="MATH"><B><IMG  WIDTH="27" HEIGHT="16" ALIGN="BOTTOM" BORDER="0"  SRC="img2242.png"  ALT="$ LU$"></B></SPAN> decomposition, however, I was not able to run either of them so far. PARDISO is the Intel proprietary solver and is about a factor of two faster than SPOOLES. The most recent solver we tried is the freeware solver PaStiX from INRIA. It is really fast and can use the GPU. For large problems and a high end Nvidea graphical  card (32 GB of RAM) we got an acceleration of a factor between 3 and 8  compared to PARDISO. We modified PaStiX for this, therefore you have to  download PaStiX from our website and compile it for your system. This can be  slightly tricky, however, it is worth it!  <P> If the MATRIXSTORAGE option is used, the stiffness and mass matrices are stored in files jobname.sti and jobname.mas, respectively. These are ASCII files containing the nonzero entries (occasionally, they can be zero; however, none of the entries which are not listed are nonzero). Each line consists of two integers and one real: the row number, the column number and the corresponding value. The entries are listed column per column. In addition, a file jobname.dof is created. It has as many entries as there are rows and columns in the stiffness and mass matrix. Each line contains a real number of the form &ldquo;a.b&rdquo;. Part a is the node number and b is the global degree of freedom corresponding to selected row. Notice that the program stops after creating these files. No further steps are treated. Consequently, *FREQUENCY, MATRIXSTORAGE only makes sense as the last step in a calculation.   <P> The parameter STORAGE indicates whether the eigenvalues, eigenmodes, mass and stiffness matrix should be stored in binary form in file jobname.eig for further use in a *MODAL DYNAMICS, *STEADY STATE DYNAMICS or *SENSITIVITY procedure. Default is STORAGE=NO. Specify STORAGE=YES if storage is requested.  <P> The parameters GLOBAL and CYCMPC only make sense in the presence of SOLVER=MATRIXSTORAGE. GLOBAL indicates whether the matrices should be stored in global coordinates, irrespective of whether a local coordinates system for any of the nodes in the structure was defined. Default is GLOBAL=YES. For GLOBAL=NO the matrices are stored in local coordinates and the directions in file jobname.dof are local directions. Notice that the GLOBAL=NO only works if no single or multiple point constrains were defined and one and the same coordinate system was defined for ALL nodes in the structure. The second parameter (CYCMPC) specifies whether any cyclic multiple point constraints should remain active while assembling the stiffness and mass matrix before storing them. Default is CYCMPC=ACTIVE. CYCMPC=INACTIVE means that all cyclic MPC's and any other MPC's containing dependent nodes belonging to cyclic MPC's are removed before assembling the matrices. The CYCMPC parameter only makes sense if GLOBAL=YES, since only then are MPC's allowed.   <P> For the iterative eigenvalue procedure ARPACK [44] is used. The eigenfrequencies are always stored in file jobname.dat.   <P> At the start of a frequency calculation all single point constraint boundary conditions, which may be zero due to previous steps, are set to zero.  <P><P> <BR>  <P> First line:  <UL> <LI>*FREQUENCY </LI> </UL> Second line:  <UL> <LI>Number of eigenfrequencies desired. </LI> <LI>Lower value of requested eigenfrequency range (in cycles/time; default:0). </LI> <LI>Upper value of requested eigenfrequency range (in cycles/time; default: <SPAN CLASS="MATH"><B><IMG  WIDTH="20" HEIGHT="14" ALIGN="BOTTOM" BORDER="0"  SRC="img2393.png"  ALT="$ \infty$"></B></SPAN>). </LI> </UL>  <P> <PRE>
Example:

*FREQUENCY
10
</PRE>  <P> requests the calculation of the 10 lowest eigenfrequencies and corresponding eigenmodes.   <P>  <P><P> <BR> Example files: beam8f, beamf.  <P>  </body></html>