Are you sure?
This action might not be possible to undo. Are you sure you want to continue?
1
Release Guide
Proprietary & Restricted Rights Notice
©
2006 UGS Corp. All Rights Reserved. This software and related documentation are proprietary to
UGS Corp. LIMITATIONS TO U.S. GOVERNMENT RIGHTS. UNPUBLISHED  RIGHTS RESERVED
UNDER THE COPYRIGHT LAWS OF THE UNITED STATES. This computer software and related
computer software documentation have been developed exclusively at private expense and are
provided subject to the following rights: If this computer software and computer software
documentation qualify as “commercial items” (as that term is defined in FAR 2.101), their use,
duplication, or disclosure by the U.S. Government is subject to the protections and restrictions as set
forth in the UGS Corp. commercial license for the software and/or documentation as prescribed in FAR
12.212 and FAR 27.405(b)(2)(i) (for civilian agencies) and in DFARS 227.72021(a) and DFARS 227.7202
3(a) (for the Department of Defense).,or any successor or similar regulation, as applicable or as
amended from time to time. If this computer software and computer documentation do not qualify as
“commercial items,” then they are “restricted computer software,” and are provided with “restrictive
rights,” and their use, duplication or disclosure by the U.S. Government is subject to the protections and
restrictions as set forth in FAR 27.404(b) and FAR 5222714 (for civilian agencies), and DFARS
227.72035(c) and DFARS 252.2277014 (for the Department of Defense), or any successor or similar
regulation as applicable or as amended from time to time. UGS Corp. , Suite 600  5800 Granite
Parkway, Plano, Texas 75024.
NASTRAN is a registered trademark of the National Aeronautics and Space Administration. NX
Nastran is an enhanced proprietary version developed and maintained by UGS Corp.
MSC is a registered trademark of MSC.Software Corporation. MSC.Nastran and MSC.Patran are
trademarks of MSC.Software Corporation.
All other trademarks are the property of their respective owners.
C O N T E N T S
NX Nastran Release Guide
1
Introduction ■ NX Nastran 4.1 Overview, 2
2
Dynamics ■ SPC/SPCD Enforced Motion, 6
❑ Introduction, 6
❑ Residual Vector Update, 6
❑ Mathematical Details for Relative Displacement Formulation, 8
❑ Updated DISPLACEMENT Bulk Data Entry, 9
❑ Updated VELOCITY Bulk Data Entry, 11
❑ Updated ACCELERATION Bulk Data Entry, 13
■ Random Response Analysis, 16
❑ Introduction, 16
❑ Theory for Crosspower Spectral Density and Crosscorrelation
Functions, 17
❑ New RCROSS Case Control Card, 19
❑ New RCROSS Bulk Data Entry, 20
3
Advanced
Nonlinear
■ Improvements to the Contact Algorithm, 24
❑ Updated NXSTRAT Card, 25
4
Miscellaneous
Enhancements
■ SurfacetoSurface Gluing, 38
❑ Introduction, 38
❑ Defining Glue Regions (BSURF, BCPROP and BSURFS Bulk
Entries), 38
❑ Defining Glue Pairs (New BGSET Case Control and Bulk
Entry), 39
❑ New BGSET Case Control Card, 40
❑ New BGSET Bulk Data Entry, 40
■ Improvements to AUTOMPC, 42
NX Nastran Release
Guide
❑ Updated Version of the AUTOMPC Parameter, 43
■ Automatic Resubmitting of NX Nastran Jobs, 44
■ Improvements to AUTOSPC, 45
A
Upward
Compatibility
■ DMAP Module Additions/Changes from NX Nastran 4.0 to 4.1, 48
■ Datablock Additions/Changes from NX Nastran 4.0 to 4.1, 55
B
System
Descriptions
■ Supported System Configurations for NX Nastran 4.1, 60
MSC.Nastran 2001 Release Guide
CHAPTER
1
Introduction
■ NX Nastran 4.1 Overview
2
1.1 NX Nastran 4.1 Overview
This section presents a short overview of the features introduced in NX Nastran
4.1.
Chapter 1, Introduction. Gives an overview of new features in NX Nastran 4.1.
Chapter 2, Dynamics. Features related to dynamic analysis have been
implemented in this release. These features are summarized below:
• SPC/SPCD Enforced Motion. The current SPC/SPCD enforced motion
capability has been enhanced to replace the current “absolute”
displacement formulation with a “relative” displacement formulation.
This enhancement will eliminate the need for automatic residual vector
generation (which was done in the 4.0 release). In addition to the relative
motion calculation, new output control options have been added to the
DISPLACEMENT, VELOCITY, and ACCELERATION case control
entries to designate whether you want absolute (default) or relative
output.
• Random Response Analysis. The new RCROSS case control and bulk
data commands are now available for requesting CrossPower Spectral
Density output.
Chapter 3, Advanced Nonlinear. This chapter describes new enhancements as
related to solutions 601 and 701:
• Improvements to the contact algorithm. The contact algorithm used in
SOL 601 and 701 has been updated with a new contact segment option.
Specifically, the order of the segments created will match the order of the
elements thus improving the output of contact results.
Chapter 4, Miscellaneous Enhancements. This chapter summarizes other useful
enhancements that do not fit into the previously mentioned categories and covers
the following topics:
• SurfacetoSurface Gluing. A new option to “glue” element faces
together during a solution is available in this release of NX Nastran.
3 CHAPTER 1
Introduction
• Improvements to AUTOMPC. Performance improvements have been made
to the AUTOMPC capability introduced in NX Nastran 3. The best
performance improvements are seen with models containing large numbers
of MPC equations. Also, a new option is available to force a degreeof
freedom (dof), which is included in an MPC equation, to be part of the mset.
You can now force a dof to be included, or not be included in the mset.
• New AUTOSPC method is available. The new AUTOSPC method Singular
Value Decomposition (SVD) is now available. The eigenvalue method is the
default, but SVD can be selected by including the new system cell SVDSPC=1.
The SVD method is numerically more reliable and should be turned on in
cases when you find unexpected singularities remaining after the AUTOSPC
operation.
• Automatic Resubmitting of NX Nastran Jobs. A new option is available to
automatically resubmit jobs which fail to run because of a failed license
request. The program will retry the job every minute up to the value of the
new AUTHQUEUE keyword.
Appendix A, Upward Compatibility. This section contains the DMAP and Datablock
changes from NX Nastran 4.0 to NX Nastran 4.1.
Appendix B, System Descriptions. This section contains a list of the system
configurations which NX Nastran supports for this release.
4
MSC.Nastran 2001 Release Guide
CHAPTER
2
Dynamics
■ SPC/SPCD Enforced Motion
■ Random Response Analysis
6
2.1 SPC/SPCD Enforced Motion
Introduction
The SPC/SPCD method of enforced motion allows the direct specification of
displacements, velocities, or accelerations via SPC/SPC1/SPCD data, thus
eliminating the need to employ large mass or Lagrange Multipliers. Though it is
a more straightforward method as compared to the large mass method of
enforced motion, the current SPC/SPCD method using the absolute
displacement formulation has shown to give poor results under certain
circumstances, particularily when damping is included.
To correct these problems, a new “relative” displacement formulation has been
introduced in this release to replace the current “absolute” displacement
formulation. As the name implies, it is now based on a relative motion approach
versus the absolute motion approach.
With the new relative approach, the issues associated with the SPC/SPCD
method have been resolved, thus the SPC/SPCD method may now be
considered as the enforced motion method of choice.
In addition to the formulation change, the new describers ABS/REL have been
added to the DISPLACEMENT, VELOCITY, and ACCELERATION case control
entries. Having these options on each entry allows you the flexibility to request,
for example, relative displacement output with absolute acceleration output in
the same run. They are also supported on a subcase level to allow for different
output requests in different subcases. The updated DISPLACEMENT,
VELOCITY, and ACCELERATION case control entries are included at the end
of this section.
Residual Vector Update
In NX Nastran version 4.0, there was a change to make residual vector
generation happen automatically when there was enforced motion present. This
was done to improve enforced motion results.
With the new relative displacement formulation in release 4.1, the enforced
motion results are of good quality without the addition of residual vector
generation. Residual vector generation is no longer automatic in this release, and
you are required to use PARAM,RESVEC,YES and PARAM, RESVINER,YES if
you want residual vector creation to occur. Below are the updated parameters
showing their new defaults:
7 CHAPTER 2
Dynamics
RESVEC Default=NO (Default updated to NO for SOL 111 & 112 when
enforced motion is present.)
By default, residual vectors are not computed. If you want
residual vectors due to:
• applied loads (LOAD or LOADSET Case Control
commands) then specify PARAM,RESVEC,YES.
• inertial loads (unit acceleration of mass) then
specify PARAM,RESVINER,YES.
• unit loads, then specify USETi,U6 entries at the
desired dofs and PARAM,RESVEC,YES.
If the model is unrestrained, you will need to supply
SUPORTi entries.
Related parameters are:
PARAM
name
Default
Value
Description
RESVEC NO Augment static shapes due to
applied loads.
RESVINER NO Augment static shapes due to
inertial loads (unit acceleration of
mass).
RESVSO YES Reorthogonalize static shapes with
mode shapes. If the stiffness is
wellconditioned, this is not
required.
RESVSE NO Print strain energy of the static
shapes.
RESVSLI YES Remove linearly dependent shapes.
RESVINER Default=NO (Default = NO for SOL 111 & 112 when enforced
motion is present.)
See related parameter RESVEC.
8
Mathematical Details for Relative Displacement
Formulation
The SPC/SPCD enforced motion formulation uses an absolute displacement
formulation per the equation:
where:
M,C,K = mass, damping, and stiffness matrices
= absolute displacements of the fset dof
= loads applied to the fset dof
= applied enforced motion
The damping loading term is not included.
The absolute displacement formulation equation will be replaced by the more
accurate enforced motion equations:
where = relative displacement of the fset dof.
Using the two equations above requires that the residual vector be computed
from the term:
If there is discrete damping present, an additional residual vector will be
computed from the term:
The damping loading term will also be included,
although this term will not have a large impact since the damping is usually
specified in terms of modal diagonal damping.
M
ff
u
··
f
C
ff
u
·
f
K
ff
u
f
+ + P
f
M
fs
u
··
s
C
fs
u
·
s
K
fs
u
s
+ + ( ) – =
u
f
P
f
u
s
C
fs
u
·
s
M
ff
y
··
f
C
ff
y
·
f
K
ff
y
f
+ + P
f
M
ff
K
ff
1
K
fs
– M
fs
+ ( )u
··
s
– C
ff
K
ff
1
K
fs
– C
fs
+ ( )u
·
s
– =
u
f
y
f
K
ff
1
K
fs
u
s
– =
y
f
M
ff
K
ff
1
K
fs
– M
fs
+
C
ff
K
ff
1
K
fs
– C
fs
+
C
ff
K
ff
1
K
fs
– C
fs
+ ( )u
·
s
9 CHAPTER 2
Dynamics
Updated DISPLACEMENT Bulk Data Entry
Requests the form and type of displacement or pressure vector output. Note: PRESSURE and
VECTOR are equivalent commands.
Format:
Examples:
DISPLACEMENT=5
DISPLACEMENT(REAL)=ALL
DISPLACEMENT(SORT2, PUNCH, REAL)=ALL
DISPLACEMENT Displacement Output Request
Describers Meaning
SORT1 Output will be presented as a tabular listing of grid points for
each load, frequency, eigenvalue, or time, depending on the
solution sequence.
SORT2 Output will be presented as a tabular listing of load, frequency
or time for each grid point.
PRINT The printer will be the output medium.
PUNCH The punch file will be the output medium.
PLOT Generates, but does not print, displacement data.
REAL or IMAG Requests rectangular format (real and imaginary) of complex
output. Use of either REAL or IMAG yields the same output.
PHASE Requests polar format (magnitude and phase) of complex
output. Phase output is in degrees.
ABS For enforced motion dynamic analysis, displacement results
will be output as absolute displacement.
DISPLACEMENT
SORT1
SORT2
PRINT, PUNCH
PLOT
REAL or IMAG
PHASE
ABS
REL
. . .
\ .

 
PSDF
ATOC
RALL
ALL
n
NONE
¹ )
¦ ¦
´ `
¦ ¦
¦ ¹
=
10
Remarks:
1. Both PRINT and PUNCH may be requested.
2. The type of analysis determines which “SORT” is the default:
• SORT1 is the default in static analysis, frequency response, steady
state heat transfer analysis, real and complex eigenvalue analysis,
flutter analysis, and buckling analysis.
• SORT2 is the default in transient response analysis (structural and
heat transfer). SORT2 is not available for real eigenvalue (including
buckling), complex eigenvalue, or flutter analysis. If SORT1 is selected
in a transient solution for one or more of the commands ACCE, DISP,
ENTH, FORC, HDOT, MPCF, OLOA, SPCF, STRA, STRE, and VELO,
then the remaining commands will also be output in SORT1 format. If
SORT2 is selected in a frequency response solution for one or more of
the commands ACCE, DISP, FORC, MPCF, OLOA, SPCF, STRA,
STRE, and VELO then the remaining commands will also be output in
SORT2 format.
• XY plot requests will force SORT2 format overriding SORT1 format
requests.
REL For enforced motion dynamic analysis, displacement results
will be output relative to the enforced motion input.
PSDF Requests the power spectral density function be calculated for
random analysis postprocessing. The request must be made
above the subcase level and RANDOM must be selected in the
Case Control. See Remark 8.
ATOC Requests the autocorrelation function be calculated for random
analysis postprocessing. The request must be made above the
subcase level and RANDOM must be selected in the Case
Control. See Remark 8.
RALL Requests that power spectral density function and the
autocorrelation function be calculated for random analysis
postprocessing. The request must be made above the subcase
level and RANDOM must be selected in the Case Control. See
Remark 8.
ALL Displacements for all points will be output.
NONE Displacement for no points will be output.
n Set identification of a previously appearing SET command.
Only displacements of points with identification numbers that
appear on this SET command will be output. (Integer>0)
Describers Meaning
11 CHAPTER 2
Dynamics
3. VECTOR and PRESSURE are alternate forms and are entirely equivalent to
DISPLACEMENT.
4. DISPLACEMENT=NONE overrides an overall output request.
5. The PLOT option is used when curve plots are desired in the magnitude/phase
representation and no printer output request is present for magnitude/phase
representation.
6. The units of translation are the same as the units of length of the model. Rotations
are in units of radians.
7. Displacement results are output in the global coordinate system (see field CD on the
GRID Bulk Data entry).
8. The PSDF, ATOC, and RALL options are for future support of random analysis
postprocessing. They provide no output to the .f06.
Remarks related to SOLs 601 and 701:
1. Output is restricted to REAL format. IMAG, PHASE, PSDF, ATOC and RALL are
ignored.
2. Displacements, velocities and accelerations must be output for the same set of grid
points if requested. Output requested for set n in this command will be combined
with the sets requested in the VELOCITY and ACCELERATION commands, and
displacements will be output at the grid points of the combined set.
Updated VELOCITY Bulk Data Entry
Requests the form and type of velocity vector output.
Format:
Examples:
VELOCITY Velocity Output Request
VELOCITY
SORT1
SORT2
PRINT, PUNCH
PLOT
REAL or IMAG
PHASE
,
ABS
REL
,
PSDF
ATOC
RALL
. .
\ .



 
ALL
n
NONE
¹ )
¦ ¦
´ `
¦ ¦
¦ ¹
=
12
VELOCITY=5
VELOCITY(SORT2,PHASE,PUNCH)=ALL
Describers Meaning
SORT1 Output will be presented as a tabular listing of grid points for
each load, frequency, eigenvalue, or time, depending on the
solution sequence.
SORT2 Output will be presented as a tabular listing of frequency or
time for each grid point.
PRINT The printer will be the output medium.
PUNCH The punch file will be the output medium.
PLOT Generates, but does not print, velocities.
REAL or IMAG Requests rectangular format (real and imaginary) of complex
output. Use of either REAL or IMAG yields the same output.
PHASE Requests polar format (magnitude and phase) of complex
output. Phase output is in degrees.
ABS For enforced motion dynamic analysis, velocity results will be
output as absolute velocity.
REL For enforced motion dynamic analysis, velocity results will be
output relative to the enforced motion input.
PSDF Requests the power spectral density function be calculated
and stored in the database for random analysis
postprocessing. The request must be made above the subcase
level and RANDOM must be selected in the Case Control.
ATOC Requests the autocorrelation function be calculated and stored
in the database for random analysis postprocessing. The
request must be made above the subcase level and RANDOM
must be selected in the Case Control.
RALL Requests that both the power spectral density function and
the autocorrelation function be calculated and stored in the
database for random analysis postprocessing. The request
must be made above the subcase level and RANDOM must be
selected in the Case Control.
ALL Velocity for all solution points will be output.
NONE Velocity for no solution points will be output.
n Set identification of a previously appearing SET command.
Only velocities of points with identification numbers that
appear on this SET command will be output. (Integer>0)
13 CHAPTER 2
Dynamics
Remarks:
1. Both PRINT and PUNCH may be requested.
2. Velocity output is only available for transient and frequency response problems.
3. See Remark 2 under “DISPLACEMENT” on page 9 for a discussion of SORT1 and
SORT2.
4. VELOCITY=NONE overrides an overall output request.
5. The PLOT option is used when curve plots are desired in the magnitude/phase
representation and no printer request is present for the magnitude/phase
representation.
6. Velocity results are output in the global coordinate system (see field CD on the
GRID Bulk Data entry).
7. The PSDF, ATOC, and RALL options are for future support of random analysis
postprocessing. They provide no output to the .f06.
Remarks related to SOLs 601 and 701:
1. Output is restricted to REAL format. IMAG, PHASE, PSDF, ATOC and RALL are
ignored.
2. Displacements, velocities and accelerations must be output for the same set of grid
points if requested. Output requested for set n in this command will be combined
with the sets requested in the DISPLACEMENT and ACCELERATION commands,
and velocities will be output at the grid points of the combined set.
Updated ACCELERATION Bulk Data Entry
Requests form and type of acceleration vector output.
Format:
Examples:
ACCELERATION Acceleration Output Request
ACCELERATION
SORT1
SORT2
PRINT, PUNCH
PLOT
REAL or IMAG
PHASE
ABS
REL
PSDF
ATOC
RALL
. . . .
\ .



 
ALL
n
NONE
¹ )
¦ ¦
´ `
¦ ¦
¦ ¹
=
14
ACCELERATION=5
ACCELERATION(SORT2, PHASE)=ALL
ACCELERATION(SORT1, PRINT, PUNCH, PHASE)=17
Describers Meaning
SORT1 Output will be presented as a tabular listing of grid points for
each load, frequency, eigenvalue, or time, depending on the
solution sequence.
SORT2 Output will be presented as a tabular listing of frequency or
time for each grid point.
PRINT The printer will be the output medium.
PUNCH The punch file will be the output medium.
PLOT Computes, but does not print or punch, acceleration output.
REAL or IMAG Requests rectangular format (real and imaginary) of complex
output. Use of either REAL or IMAG yields the same output.
PHASE Requests polar format (magnitude and phase) of complex
output. Phase output is in degrees.
ABS For enforced motion dynamic analysis, acceleration results will
be output as absolute acceleration.
REL For enforced motion dynamic analysis, acceleration results will
be output relative to the enforced motion input.
PSDF Requests the power spectral density function be calculated for
random analysis postprocessing. The request must be made
above the subcase level and RANDOM must be selected in the
Case Control.
ATOC Requests the autocorrelation function be calculated for random
analysis postprocessing. The request must be made above the
subcase level and RANDOM must be selected in the Case
Control.
RALL Request both the power spectral density function and
autocorrelation function be calculated for random analysis
postprocessing. The request must be made above the subcase
level and RANDOM must be selected in the Case Control.
ALL Accelerations at all points will be output.
NONE Accelerations at no points will be output.
n Set identification of a previously appearing SET command.
Only accelerations of points with identification numbers that
appear on this SET command will be output. (Integer>0)
15 CHAPTER 2
Dynamics
Remarks:
1. Both PRINT and PUNCH may be requested.
2. Acceleration output is only available for transient and frequency response
problems.
3. See Remark 2 under “DISPLACEMENT” on page 9 for a discussion of SORT1 and
SORT2.
4. ACCELERATION=NONE allows overriding an overall output request.
5. The PLOT option is used when curve plots are desired in the magnitude/phase
representation and no printer request is present for magnitude/phase
representation.
6. Acceleration results are output in the global coordinate system (see field CD on the
GRID Bulk Data entry).
7. The PSDF, ATOC, and RALL options are for future support of random analysis
postprocessing. They provide no output to the .f06.
Remarks related to SOLs 601 and 701:
Output is restricted to REAL format. IMAG, PHASE, PSDF, ATOC and
RALL are ignored.
16
2.2 Random Response Analysis
Introduction
In many applications, the loading on a structure is not known in a definite (or
deterministic) sense, and instead is quantified in a statistical sense with properties
such as the mean load and standard deviation of load. Such loadings are known
as random or stochastic loads. Examples of random loads include: rough road
surface loads on automobiles, ocean wave loads on offshore platforms, wind
loads on buildings, vibration loads from rocket engines, and earthquake ground
motions.
It should be expected that the response of the structure due to random loads will
also be random in nature and analysis methods that determine the statistical
properties of response are appropriate. The most commonly used approach for
random analysis uses Power Spectral Density (PSD) functions to define loading
and the calculated response. A PSD function describes how the variance of a time
series of the product of two variables is distributed with frequency. If the two
variables are the same, the PSD function is known as an auto spectrum, if the
variables are different, the PSD function is called a cross spectrum.
NX Nastran has the capability for performing random analysis. The procedure is
a twostep process in which first a frequency response analysis is performed to
calculate transfer functions which are the ratio of output to a unit input. In the
second step, the PSD loading function is used to scale the transfer functions to
compute the random PSD response. The input PSD functions represent the
statistics of the applied loads. If there are several applied loads and they are
uncorrelated from each other, only the auto spectra of the loads need be applied.
If on the other hand the loads are not independent of each other, the cross
spectrum of the loads need also be input to define the correlation of the loadings.
Note that although the process is described as two steps, it can be performed with
NX Nastran as only one solution submittal.
Random response output consists of the response PSD, autocorrelation functions,
number of zero crossings with positive slope per unit time, and RMS (rootmean
square) values of response. Up until the release of NX Nastran version 4.0, only
auto spectrum PSD functions of response could be output for random results.
Users were required to use DMAP methods if they were interested in obtaining
cross spectrum results. Now with NX Nastran 4.1, it is possible to request cross
spectrum output using standard PSD solutions. A new Case Control command,
RCROSS and Bulk Data entry, RCROSS have been created for this purpose.
Formats of these entries are in included at the end of this section.
17 CHAPTER 2
Dynamics
The following examples have been provided in the install location
NX_Nastran_Install_Path/nxn4/nast/tpl to demonstrate capabilities and to show the
correct syntax for using the new RCROSS commands: rcross01.dat, rcross02.dat,
rcross03.dat, rcross04.dat.
Theory for Crosspower Spectral Density and Cross
correlation Functions
Assuming that a random process is ergodic, the cross correlation function between a
pair of time records u
a
(t) and u
b
(t) is defined as
where u
a
(t) and u
b
(t) can be displacement, velocity, acceleration or singlepoint
constraint force responses at the same or different grid points; or stress, strain, and
force components in the same or different elements. The assumption of ergodicty
means that as the length of the record is increased the average approaches the
corresponding ensemble averages. The operation of integration over a time record of
length and dividing that quantity by represents an averaging process over time.
If we denote the Fourier transform of a time history as
we can define the crosspower spectral density (crossPSD) as
where is angular frequency in rad/sec and the symbol (*) denotes complex
conjugate. Simply stated, the crossPSD is the product of the Fourier transform of two
records.
It can be shown using equations (1) and (2) that the cross correlation function and
cross spectrum are related as Fourier transform pairs given as
It is noted that the cross correlation function is always real valued and the cross
spectrum function is in general complex valued. In addition, it can be shown to
possess the following properties:
R
ab
τ ( )
lim
T ∞ →
1
T
 u
a
t ( )u
b
t τ – ( )dt (1)
0
T
∫
=
T T
U
a
ω,T ( ) u
a
t ( )e
iwt –
dt (2)
0
T
∫
=
S
ab
ω ( )
lim
T ∞ →
2
T
 U
a
ω,T ( ) U
b
*
ω,T ( ) (3) =
ω
S
ab
ω ( ) 2 R
ab
τ ( )e
i ωt –
dτ
∞
∞
∫
(4) =
R
ab
τ ( )
1
4π
 S
ab
ω ( )e
i ωt
dω (5)
∞
∞
∫
=
R
ab
τ – ( ) R
ba
τ ( ) (6) =
18
It should also be noted that we have been referring to the general case where u
a
(t)
and u
b
(t) are different responses. In many situations, only a single response,
rather than the joint response is of interest. In that case, autocorrelation functions,
, and autospectrum functions, , are computed. The autospectrum
by definition is completely real.
Returning to the more general case, we can rewrite in terms of its real and
imaginary parts as
From the properties in equation (5) it can be determined that is an even
function of and is an odd function of .
Substituting equation (8) into the equation (7) and recalling that
, it can be shown that
A particular case of interest is the value of the crosscorrelation function for
. As evidenced by equation (1) it represents the mean cross product. Using
equation (9) it can be computed as
where denotes mean average.
The mean cross product is an important statistical quantity. For crosscorrelation
functions, is it known as the covariance. For autocorrelation functions the mean
crossproduct is known as the variance and its square root is the standard
deviation. By using the standard assumption that loadings and response are
Gaussian (normally distributed), knowing the covariance allows you to define the
probability distribution and thus determine likelihood of occurrence of response
levels. For example, if the standard deviation of response u
a
(t) is determined to be
, the likelihood that at any time the response is less than is 99.9%.
S
ab
ω – ( ) S
ba
ω ( ) S
ab
*
ω ( ) (7) = =
R
aa
τ ( ) S
aa
ω ( )
S
ab
ω ( )
S
ab
ω ( ) S
ab
r
ω ( ) i S
ab
i
ω ( ) (8) + =
S
ab
r
ω ( )
ω S
ab
i
ω ( ) ω
e
i ωt
ωt ( ) cos i ωt ( ) sin + =
R
ab
τ ( )
1
2π
 S
ab
r
ω ( ) ωτ ( ) cos S
ab
i
ω ( ) ωτ ( ) sin –  dω (9)
0
∞
∫
=
τ 0 =
R
ab
0 ( )
1
2π
 S
ab
r
ω ( )dω = u
a
t ( )u
b
t ( ) 10 ( )
0
∞
∫
=
( )
σ
a
3σ
a
19 CHAPTER 2
Dynamics
If a system is subject to multiple sources of excitation, the crossPSD of responses u
a
(t)
and u
b
(t) is related to the crossPSDs of the excitation sources and the frequency
response functions by the equation
where is the crossPSD of loadings P
j
(t) and P
k
(t). is the frequency
response function of u
a
(t) corresponding to the excitation source P
j
(t) and similarly
is the complex conjugate of the frequency response function of u
b
(t)
corresponding to the excitation source P
k
(t). If the two excitation sources are not
correlated, we have .
New RCROSS Case Control Card
Requests computation and output of crosspower spectral density functions in random
analysis.
Format:
Examples:
RCROSS(PHASE) = 10
RCROSS(PSDF,NOPRINT,PUNCH) = 20
RCROSS = 30
RCROSS CrossPower Spectral Density Functions Output Request
Describers Meaning
REAL or IMAG Requests rectangular format (real and imaginary) of
complex output (for crosspower spectral density function).
Use of either REAL or IMAG yields the same output.
(Default)
PHASE Requests polar format (magnitude and phase) of complex
output (for crosspower spectral density function). Phase
output is in degrees.
PRINT Writes output to print file. (Default)
S
ab
ω ( ) H
aj
ω ( )H
bk
*
ω ( )S
jk
ω ( ) (11)
k
∑
j
∑
=
S
jk
ω ( ) H
aj
ω ( )
H
bk
*
ω ( )
S
jk
ω ( ) 0 =
RCROSS
REAL or IMAG
PHASE

PRINT
NOPRINT
 PUNCH   PSDF   . . .
\ .
 
n =
20
Remarks:
1. The case control RCROSS entry must be used in conjuction with the case
control RANDOM entry. See remarks under the RANDOM case control
entry.
2. Response quantities, such as DISPLACEMENT, STRESS, and FORCE, must be
requested by corresponding case control entries in order to compute cross
power spectral density between the two response quantities specified by the
RCROSS bulk data entry. It is recommended that the DISPLACEMENT,
STRESS, and FORCE requests be put above the subcase level to ensure that
these response quantities exist when the random analysis postprocessing
occurs.
3. The response quantities must belong to the same superelement. The cross
power spectral density functions between two responses that belong to
different superelements are not supported.
New RCROSS Bulk Data Entry
Defines a pair of response quantities for computing the crosspower spectral density
functions in random analysis.
Format:
Example:
NOPRINT Does not write output to the print file.
PUNCH Writes output to punch file.
PSDF Requests the crosspower spectral density function be
calculated and output for random analysis postprocessing.
(Default)
n Identification number of RCROSS bulk data entry to be used
in random analysis. (Integer >0)
RCROSS
CrossPower Spectral Density Functions Output
1 2 3 4 5 6 7 8 9 10
RCROSS SID RTYPE1 ID1 COMP1 RTYPE2 ID2 COMP2 CURID
RCROSS 20 DISP 50 2 STRESS 150 8 4
Describers Meaning
21 CHAPTER 2
Dynamics
Remarks:
1. This entry is required for computing the crosspower spectral density function. SID
must be selected with the case control command (RCROSS=SID). Fields RTYPE1,
ID1, and COMP1 represent the first response quantity; fields RTYPE2, ID2, and
COMP2 represent the second response quantity.
2. The keywords for field RTYPEi are listed as follows:
If either RTYPE1 or RTYPE2 is blank, then the blank field takes the default from the defined
field.
Field Contents
SID Case control RCROSS identification number for crosspower spectral
density function. (Integer>0)
RTYPEi Type of response quantity. At least one field must be selected. See
remark 2. (Character or blank)
IDi Element, grid, or scalar point identification number. (Integer > 0)
COMPi Component code (item) identification number. See remark 3. (Integer
> 0)
CURID Curve identification number. See remark 4. (Integer > 0 or blank)
Keyword Meaning
DISP Displacement Vector
VELO Velocity Vector
ACCEL Acceleration Vector
OLOAD Applied Load Vector
SPCF Singlepoint Constraint Force
Vector
MPCF Multipoint Constraint Force
Vector
STRESS Element Stress
STRAIN Element Strain
FORCE Element Force
22
3. For elements, the item code COMPi represents a component of the element
stress, strain or force and is described in Tables “Element StressStrain Item
Codes” and “Element Force Item Codes”. For an item having both a real and
imaginary part, the code of the real part must be selected.
For grid points, the item code is one of 1,2,3,4,5, and 6, which represent the
mnemonics T1, T2, T3, R1, R2, and R3, respectively. For scalar points, always
use 1.
4. Field CURID is optional. It is for your convenience to identify the output by
using a single index.
MSC.Nastran 2001 Release Guide
CHAPTER
3
Advanced Nonlinear
■ Improvements to the Contact Algorithm
24
3.1 Improvements to the Contact Algorithm
When contact definitions exist in an Advanced Nonlinear Solution (SOLs 601
and 701), contact segments are created during the solution in the regions where
contact has been defined. These contact segments are created on the shell and
solid element faces.
A new contact segment option is available for SOL 601 in NX Nastran 4.1 that
gives improved contact results. Specifically, the order of the segments created
(linear or quadratic) will match the order of the elements. When quadratic
contact segments are created on quadratic elements, the resulting contact
tractions are significantly better.
The new parameter CSTYPE has been created on the bulk data entry NXSTRAT
to support the new contact segment creation.
CSTYPE=1 is more accurate and will give better contact traction results,
expecially when used with quadratic elements (for example, 10grid tetrahedral
elements). However, certain restrictions apply in NX Nastran 4.1 when
CSTYPE=1 is used. These restrictions, listed below, will be eliminated in future
releases. Note that the default settings comply with the restrictions.
• Only constraint function algorithm (default) may be used, i.e., TYPE=0
in BCTPARA
• Contact surface offset must be zero (default), i.e., OFFSET=0.0 in
BCTPARA
• Only singlesided contact (default) is allowed, i.e., NSIDE=1 in
BCTPARA
• Only frictionless contact (default) or regular Coulomb friction is
allowed, i.e., FRICMOD=0 or 1 in BCTPARA
• No tied contact (default), i.e., TIED=0 in BCTPARA
• Consistent contact stiffness cannot be used, i.e., CSTIFF=0 in
BCTPARA
• Continuous normal must be used (default), i.e., SEGNORM=0 or 1 in
BCTPARA
CSTYPE Selects the type of contact segment to use. (Integer; Default = 0)
0  Use the old type of contact segment.
1  Use the new type of contact segment.
25 CHAPTER 3
Advanced Nonlinear
• Initial penetration cannot be ignored (default), i.e., INIPENE=0 or 1 in
BCTPARA
Updated NXSTRAT Card
(This includes a change to the param LSEARCH which is not specifically related to the
contact output improvements.)
Defines parameters for solution control and strategy in advanced nonlinear structural
analysis.
Format:
Example:
NXSTRAT
Strategy Parameters for SOLs 601 and 701
1 2 3 4 5 6 7 8 9 10
NXSTRAT ID Param1 Value1 Param2 Value2 Param3 Value3
Param4 Value4 Param5 Value5 etc
NXSTRAT 1 AUTO 1 MAXITE 30 RTOL 0.005
ATSNEXT 3
Field Contents
ID Identification number. Currently not used. (Integer > 0)
PARAMi Name of the NXSTRAT parameter. Allowable names are given in
Table 81. See remark 1 for parameters applicable to SOL 701.
(Character)
VALUEi Value of the parameter. See Table 81. (Real or integer)
26
Table 81 NXSTRAT Parameters
Name Description
Analysis Control Parameters
SOLVER Selects the solver to use. (Integer; Default = 0)
0 – Direct sparse solver
1 – Multigrid solver
AUTO Indicates whether automatic incrementation scheme is enabled.
(Integer; Default = 0)
0 – No automatic incrementation scheme is used
1 – Automatic time stepping (ATS) scheme is enabled
2 – Automatic loaddisplacement control (LDC) scheme is enabled
NPOSIT Indicates whether analysis continues when the system matrix is
not positive definite. (Integer; Default = 0)
0 – Analysis may stop
1 – Analysis continues
Notes:
If NPOSIT=0, analysis stops unless
the ATS or LDC scheme is enabled; i.e. AUTO=1 or AUTO=2
contact analysis is being performed
It is not recommended to set NPOSIT=1 for a linear analysis.
MASSTYP Selects the type of mass matrix to be used in dynamic analysis.
(Integer; Default = 1)
0 – Lumped mass is used
1 – Consistent mass is used
Analysis Options
TINT
*
Integration order for the local tdirection (through thickness) of
shell elements with elastoplastic materials. By default, 5point
NewtonCotes is used for singlelayered shell and 3point
NewtonCotes is used for multilayered shell. Note that 2point
Gauss integration is always used for all shell elements with elastic
materials. (Integer; Default = 0).
1 < TINT < 6 – Gauss integration method with integration order
TINT
3, 5, 7 – NewtonCotes integration with order TINT
ICMODE
*
Indicates whether incompatible modes are used for 4node shell
elements. (Integer; Default =1 for SOL 601 and 0 for SOL 701)
0  Incompatible modes are not used
1  Incompatible modes are used
27 CHAPTER 3
Advanced Nonlinear
MSTAB Indicates whether the stiffness matrix stabilization feature is used.
(Integer; Default = 0)
0 – Matrix stabilization is not used
1 – Matrix stabilization is used
MSFAC Matrix stabilization factor. (Real; Default = 1.0E12)
DTDELAY
*
Element death time delay. (Real; Default = 0.0)
When an element is too deformed and becomes “dead”, its
contribution to the overall stiffness of the structure is removed. By
specifying DTDELAY > 0.0, the contribution from the element
stiffness is gradually reduced to zero over time DTDELAY instead
of being suddenly removed. This may help in the convergence of
the solution.
SDOFANG
*
Angle used to determine whether a shell midsurface node is
assigned 5 or 6 degrees of freedom. (Real; Default = 5.0)
UPFORM
*
Indicates whether u/p formulation is used for elements. Note that
u/p formulation is always used for hyperelastic elements and
always not used for hyperfoam elements and elastic elements
with Poisson’s ratio less than 0.48. It is also not used for gasket
elements (Integer; Default = 0)
0 – u/p formulation is not used
1 – u/p formulation is used instead of displacementbased
formulation
ULFORM
*
Indicates which large strain formulation is used for 4node shell
elements. (Integer; Default = 0)
0 – Updated LagrangianJaumann (ULJ) formulation is used if
rigidtarget algorithm contact is used or SOL 701 is run.
Otherwise, Updated LagrangianHencky (ULH) formulation is
used.
1 – Use ULH formulation
2 – Use ULJ formulation
Note: For shell elements which are not 4noded, the ULJ
formulation is always used for large strains. For 3D solid, plane
strain and axisymmetric elements, ULH formulation is always
used for large strains. In restarting from SOL 601 to 701 or vice
versa, ULFORM needs to be specified such that both analyses use
the same formulation.
Name Description
28
DISPOPT Indicates whether prescribed displacements are applied to the
original configuration or the deformed configuration. This option
is only applicable for a restart analysis or when a delay (or arrival)
time is specified for the prescribed displacement. (Integer; Default
= 0)
0 – Applied to original configuration
1 – Applied to deformed configuration
LOADOPT
*
Indicates whether prescribed loads (pressure and centrifugal) are
deformationdependent, i.e. the direction and magnitude of the
load may change due to large deformation of the structure. This
option is only applicable for large displacement analysis, i.e.
PARAM,LGDISP,1 (Integer; Default = 1)
0 – Load is independent of structural deformation
1 – Load is affected by structural deformation
Time Integration
ALPHA Alpha coefficient for the Newmark time integration method.
(Real; Default = 0.25)
DELTA Delta coefficient for the Newmark method. (Real; Default = 0.5)
SOL 701 Time Stepping
XSTEP
o
Selects time step method used in an explicit time integration
analysis. (Integer; Default = 0)
0  Time step size is calucated by the program based on the critical
time step size. The data in the selected TSTEP bulk data entry is
used to calculate the total solution time for the analysis.
1  The number of time steps and the time step size as specified in
the selected TSTEP bulk data entry is used.
XDTCAL
o
Calculation of the critical time step size may be computationally
expensive. This parameter specifies that the critical time step size
be recalculated every XDTCAL time steps. (Integer > 0, Default =
1)
XDTFAC
o
The critical time step size is calculated based on certain
assumptions. It is often necessary, especially for nonlinear
analysis, to use a time step size smaller than the calculated critical
time step size. The factor multiplied by the calculated critical time
step size gives the time step size used in the analysis. (4.0 > Real >
0.0, Default = 0.9)
Name Description
29 CHAPTER 3
Advanced Nonlinear
XMSCALE
o
Specifies the factor to scale the mass (densities) of the entire model
(at the beginning of the analysis) to increase the critical time step
size required for stability when the explicit time integration
scheme is used. See warning in Remark 2. (Real = 1.0, Default =
1.0)
XDTMIN1
o
The minimum time step size used to determine if mass scaling
will be applied to elements (at the beginning of the analysis)
whose critical time step size is smaller than DTMIN1. The amount
of mass scaling is calculated for each element so that the critical
time step size is equal to DTMIN1. See Remark 2 and warning in
Remark 3. (Real = 0.0, Default = 0.0)
XDTMIN2
o
The minimum time step size used to determine whether an
element will be removed in an explicit time integration analysis.
In explicit time integration, the smaller an element size is, the
smaller will the critical time step size be. If the critical time step
size for an element is smaller than XDTMIN2, the element will be
removed in the analysis. See Remark 2 and warning in Remark 3.
(Real > 0.0, Default = 0.0)
Multigrid Solver
ITEMAX Maximum number of iterations allowed for the multigrid solver
to converge. (Integer > 0; Default = 1000)
EPSIA Convergence tolerance EPSIA. (Real; Default = 1.0E6)
EPSIB Convergence tolerance EPSIB. (Real; Default = 1.0E4)
EPSII Convergence tolerance EPSII. (Real; Default = 1.0E8)
Equilibrium Iteration and Convergence
LSEARCH Flag to indicate the use of line searches within the iteration
scheme. (Integer; Default = 0)
0 – Line search is not used
1 – Line search is used
LSLOWER Lower bound for line search. (0.0 < Real < 1.0; Default = 0.001)
LSUPPER Upper bound for line search. (1.0 < Real; Default = 2.0)
Name Description
30
MAXITE Maximum number of iterations within a time step. If the
maximum number of iterations is reached without achieving
convergence (see CONVCRI parameter), the program will stop
unless the automatic time stepping (ATS) or load displacement
control scheme is selected (see parameter AUTO). (1 < Integer <
999; Default = 15)
CONVCRI Convergence Criteria. (Integer; Default = 0)
0 – Convergence based on energy
1 – Convergence based on energy and force
2 – Convergence based on energy and displacement
3 – Convergence based on force
4 – Convergence based on displacement
ETOL Relative energy tolerance. (Real; Default = 0.001)
RTOL Relative force (and moment) tolerance (Real; Default = 0.01)
RNORM Reference force. (Real)
RMNORM Reference moment. (Real)
RCTOL Relative contact force tolerance. (Real; Default = 0.05)
DTOL Relative displacement (translation and rotation) tolerance. (Real;
Default = 0.01)
DNORM Reference translation. (Real)
DMNORM Reference rotation. (Real)
STOL Line search convergence tolerance. (Real; Default = 0.5)
RCONSM Reference contact force. (Real; Default = 0.01)
ENLSTH Line search energy threshold. (Real; Default = 0.0)
Automatic Time Stepping (ATS) Scheme
ATSSUBD Number that limits the smallest time step size when the automatic
time stepping (ATS) scheme is used. For a time step size of DT, the
program will stop if convergence is not achieved and the next
subdivided time step size is less than DT/ATSSUBD. (Integer > 1;
Default = 10)
ATSMXDT Factor that limits the maximum time step size when the automatic
time stepping (ATS) scheme is used. The ATS scheme may
increase the time step size after convergence is achieved.
However, for a time step size of DT, the program will not use a
time step size greater than ATSMXDT * DT. (Real; Default = 3.0)
Name Description
31 CHAPTER 3
Advanced Nonlinear
ATSNEXT Flag controls what time step size to use once convergence is
reached after an ATS subdivision. (Integer; Default = 0)
0 – Automatically set by program. For contact analysis, ATSNEXT
= 2, otherwise ATSNEXT = 1.
1 – Use the time step size that gave convergence, i.e., the reduced
time step that led to convergence is used again.
2 – Return to the original time step size, i.e., the original time step
size before any subdivision took place is used.
3 – Use a time step size such that the solution time matches the
original solution time specified by the user.
ATSDFAC Division factor used calculate the subincrement time step size. If
current time step size is DT and convergence is not achieved, the
next time step size will be DT/ATSDFAC. (Real > 1.0; Default =
2.0)
ATSLOWS Flag whether a lowspeed dynamics analysis is performed instead
of a static analysis. (Integer; Default = 0)
0 – Lowspeed dynamics option is not activated
1 – Lowspeed dynamics is performed
ATSDAMP Damping factor used in lowspeed dynamics analysis. (Real > 0.0;
Default = 1.0e4)
Load Displacement Control (LDC) Scheme
LDCGRID Grid point id at which a displacement is prescribed for the first
solution step. (Integer > 0)
LDCDOF Degree of freedom for prescribed displacement at grid point
LDCGRID. (1< Integer < 6)
1 – X translation
2 – Y translation
3 – Z translation
4 – X rotation
5 – Y rotation
6 – Z rotation
LDCDISP Prescribed displacement at grid point LDCGRID for the first
solution step. (Real)
LDCIMAX Displacement convergence factor used to limit the maximum
incremental displacement during a solution step. (Real; Default =
3.0)
Name Description
32
LDCDMAX Maximum (absolute magnitude) displacement (for the degree of
freedom specified by LDCDOF) at the grid point LDCGRID
allowed during the analysis. When the displacement reaches or
exceeds LDCDMAX, the program will stop the analysis. See
Section 6.2.4 in Advanced Nonlinear Theory and Modeling Guide
for other criteria that determines when an LDC solution will stop.
(Real)
LDCCONT Flag whether the solution is terminated when the first critical
point on the equilibrium path is reached. (Integer; Default = 0)
0 – Solution stops
1 – Solution continues
LDCSUBD Maximum number of arc length subdivisions allowed. (Integer >
1; Default = 10)
Contact Control
IMPACT Impact control scheme (Integer; Default = 0)
0 – No special treatment is applied for impact problems
1 – Post impact adjustment of velocities and accelerations is
applied
2 – Modified parameters are used in Newmark time integration
scheme
NSUPP Number of iterations for pairing contactor node to target segment.
If NSUPP > 0, during the first NSUPP iterations, the pairing target
segment is recorded for each contactor node. From iteration
NSUPP+1, if a target segment in the recorded list is repeated, it is
“frozen” to be the pairing target segment for the remaining
equilibrium iterations in that time step. Specifying NSUPP > 0
may help in the convergence for certain problems.
(0 < Integer < 99; Default = 0)
RTSUBD Selects the subdivision scheme used in the implicit rigidtarget
contact algorithm when the tensile contact force is too large.
(Integer; Default = 0)
0 – Subdivision is based on the magnitude of the tensile contact
force, i.e., the larger the magnitude, the smaller will be the
subdivided time step size.
1 – Subdivision is based on the global automatic time stepping
(ATS) subdivsion settings.
CSTYPE Selects the type of contact segment to use. (Integer; Default = 0)
0  Use the old type of contact segment.
1  Use the new type of contact segment.
Name Description
33 CHAPTER 3
Advanced Nonlinear
Restart Options
MODEX
*
Indicates the mode of execution. (Integer; Default = 0)
0 – Normal analysis run, i.e. not a restart analysis
1 – Restart analysis
The restart (.res) file from a previous run must exist to do a restart
analysis. The filename and location of the restart file is determined
by the “dbs” keyword. By default, dbs points to the current
working directory with the prefix of the current job name.
TSTART
*
Solution starting time. If MODEX=1, TSTART must equal a
solution time in which data was saved in a previous run. If
TSTART = 0.0, the last time step in the restart file is used. (Real,
Default = 0.0)
IRINT
*
Frequency of saving the analysis results in the restart file. (Integer;
Default = 0)
0 – IRINT is set to 1 when implicit time integration is used and set
to the number of steps in the first time step block when explicit
time integration is used.
> 0 – Restart file is overwritten every IRINT time steps
< 0 – Restart file is appended every IRINT time steps
Other Parameters
NSUBGRP
*
Number of subgroups to divide large number of elements with
same property ID into. Normally, elements with same type and
property ID are placed into a group. If a group contains more than
1000 elements and NSUBGRP > 1, the elements are placed into
NSUBGRP subgroups for more efficient processing. (Integer > 0;
Default = 1)
Translation Options
Name Description
34
ELCV Convert 8node to 9node quadrilateral (plane strain,
axisymmetric and shell) elements and 20node to 27node brick
elements. Note that this also converts 6node to 7node triangular
(plane strain and axisymmetric) elements and 10node to 11node
tetrahedral elements. (Integer; Default = 0)
0 – No conversion of elements
1 – Convert elements as described above; nodal coincidence is not
checked against existing nodes and new generated nodes are
always created.
2 – Convert elements as described above; nodal coincidence is
checked against existing nodes and a new node will not be created
at a location if a node already exist at that location.
EQRBAR Indicates how RBAR elements are handled. (Integer; Default = 0)
0 – RBAR is simulated using rigid option in small displacement
analysis and using flexible option in large displacement analysis.
1 – RBAR is simulated using rigid option (i.e. simulated by rigid
link or constraint equations as determined by program)
2 – RBAR is simulated using flexible option (i.e. simulated by
spring or beam elements as determined by program)
3 – RBAR is simulated by spring elements
See Section 2.7 of Advanced Nonlinear Theory and Modeling
Guide for details on how RBAR elements are handled.
EQRBE2 Indicates how RBE2 elements are handled. (Integer; Default = 0)
0 – RBE2 is simulated using rigid option in small displacement
analysis and using flexible option in large displacement analysis.
1 – RBE2 is simulated using rigid option (i.e. simulated by rigid
links or constraint equations as determined by program)
2 – RBE2 is simulated using flexible option (i.e. simulated by
spring or beam elements as determined by program)
3 – RBE2 is simulated by spring elements
See Section 2.7 of Advanced Nonlinear Theory and Modeling
Guide for details on how RBE2 elements are handled.
SPRINGK Stiffness of spring elements that simulate RBAR or RBE2
elements. (Real, Default = 0.0)
If SPRINGK = 0.0, program automatically sets SPRINGK
according to the following calculations.
SPRINGK = EMAX * LMODEL
where EMAX = maximum Young’s Modulus of materials in the
model and LMODEL = largest dimension of the model. If no
material is specified in the model, EMAX is set to 1.0E12.
Name Description
35 CHAPTER 3
Advanced Nonlinear
Remarks:
1. Parameters applicable to SOL 701 are:
• XSTEP, XDTCAL, XDTFAC, XMSCALE, XDTMIN1 and XDTMIN2 are only used
for SOL 701. These parameters are indicated in the table with a superscript ‘
o
’.
• TINT, ICMODE, DTDELAY, SDOFANG, UPFORM, LOADOPT, MODEX,
TSTART, IRINT and NSUBGRP parameters can be used for SOL 701. These
parameters are indicated in the table with a superscript
‘*’
.
2. XMSCALE, XDTMIN1 and XDTMIN2 may be used together. XDTMIN1 and
DTMIN2 are applied after XMSCALE is applied. If XDTMIN1 and XDTMIN2 are
both used, XDTMIN1 should be greater than XDTMIN2. If XDTMIN2 = XDTMIN1
is specified, XDTMIN1 will be ignored.
3. WARNING: Specifying XMSCALE > 1.0, XDTMIN1 > 0.0 or XDTMIN2 > 0.0
may change the model significantly. Hence, extra care should be exercised in
examining the results when any of these parameters are used.
BEAME Young’s Modulus of material assigned to beam elements that
simulate RBAR or RBE2 elements. (Real, Default = 0.0)
If BEAME = 0.0, BEAME is set to EMAX * 100.0 where EMAX =
maximum Young’s Modulus of materials in the model. If no
material is specified in the model, EMAX is set to 1.0E12.
BEAMA Circular cross section area of beam elements that simulate RBAR
or RBE2 elements. (Real, Default = 0.0)
If BEAMA = 0.0, program automatically sets BEAMA according to
the following calculation:
BEAMA = (LMODEL * .01)
2
where LMODEL = largest dimension
of the model
RBLCRIT Critical length for determining how RBAR and RBE2 elements are
simulated when the rigid or flexible option is used to simulate
RBAR (see EQRBAR) and RBE2 (see EQRBE2). (Real, Default =
0.0)
If RBLCRIT = 0.0, then
• if EQRBAR (or EQRBE2) = 1,
RBLCRIT = LMODEL * 1.0E6
• if EQRBAR (or EQRBE2) = 2,
RBLCRIT = LMODEL * 1.0E3
Name Description
36
MSC.Nastran 2001 Release Guide%
CHAPTER
4
Miscellaneous Enhancements
■ SurfacetoSurface Gluing
■ Improvements to AUTOMPC
■ Automatic Resubmitting of NX Nastran Jobs
■ Improvements to AUTOSPC
38
4.1 SurfacetoSurface Gluing
Introduction
A new option to “glue” element faces together during a solution is available in
this release of NX Nastran. Glue definitions can be used in all solution sequences
except for SOL 601 and 701. The glue option creates stiff springs to connect the
predefined surfaces and prevents relative motion in all directions. For discussion
purposes, the springs created by the solver from glue definitions will be referred
to as “glue elements” in the documentation.
Predefined regions of element free faces are used to detect where the glue
elements are created. From each element free face, a normal is projected, then the
solver checks to see if any of these normals intersect with other element free faces.
A glue element is created during the solution if:
• NX Nastran finds an intersection between element faces,
• and the distance between the two faces is equal to or less than the
defined separation distance.
The following should be noted:
• Superelements can be used with surfacetosurface gluing as long as the
superelements are defined with the SESET bulk entry.
• In a linear statics solution (SOL 101), surface gluing and surface contact
can be defined for the same subcase.
• A glue set can only be defined in the global or first subcase and it will be
used in all subcases. The exception to this is when linear contact is
defined in SOL 101. For this special case, glue sets can be defined in any
subcase. This limitation will be removed in NXN5.
Defining Glue Regions (BSURF, BCPROP and BSURFS
Bulk Entries)
You must first define the regions where you would like the solver to create glue
elements. A region is a collection of element free faces in a section of the model
where you expect gluing (or contact) to occur. These regions can be created using
shell elements (BSURF and BCPROP) and using solid element free faces
(BSURFS). The BSURF entry is defined by its own unique ID and is a list or range
of shell element IDs to include in the region. The BCPROP entry is defined by its
own unique ID and is a list of shell element property IDs. Shell elements which
use any of the property IDs listed in the BCPROP entry will be included in the
39 CHAPTER 4
Miscellaneous Enhancements
region. The BSURFS entry is defined by its own unique ID and is a list of solid element
IDs each followed by 3 grid points defining which face of the 3D element to include in
the glue region. An element should not appear more than once in the regions that are
part of a glue/contact pair. The BSURF, BCPROP and BSURFS entries described are
used to define glue and/or contact regions.
When a source region is made from shell elements (BSURF or BCPROP), the SURF
field on the BCRPARA bulk entry may be needed to alter the search direction. The top
side of a shell element is determined by the order and direction of grid points on the
element’s definition and the righthand rule. (See chapter 15 of the NX Nastran User’s
Guide for information on using consistent normals) When shell elements are used as
the source in a contact pair, by default, the solve will use the top side to project the
element normal while searching for the target elements. In the case where the target is
on the bottom side, you can set the SURF option to “BOT”, and the normal will be
projected from the bottom side. Understanding shell element normals, and making
sure they are consistent in the source regions is very important to ensuring that glue
elements will be created as expected. On the BCRPARA bulk entry, CRID and SURF
are the only fields used by glue regions.
Defining Glue Pairs (New BGSET Case Control and Bulk
Entry)
Two new commands have been created in this release to define glue conditions for the
solution, the new BGSET case control command, and the new BGSET bulk entry, both
of which are included below.
A glue pair is a way to combine two regions, source and target, in which gluing will
be analyzed during the solution. The new BGSET bulk entry is used to define each
glue pair. The GSID field will need to match the value of ‘n’ on the new BGSET case
control entry for the solution to recognize this glue definition. The SIDi and TIDi fields
refer to regions created by the BSURF, BCPROP and BSURFS entries, and are used to
define source and target regions respectively for a pair. As many pairs as desired can
be included on a single BGSET entry.
The search distance field (SDIST) defines the distance in which the solver can initially
determine if the distance between element faces in a particular pair are within the
threshold for creating glue elements. The default value of SDIST of 100 is large enough
to handle most geometry situations, but can be adjusted as needed. This value is used
once, at the beginning of the solution, to determine where glue elements need to be
initially created. Recall that NX Nastran projects normals from element faces and then
checks to see if any of these normals intersect with another element free face. If the
40
projected normal intersects an element face, and the distance between the two
element faces is within the range defined on the SDIST fields, a glue element is
created.
The remaining field on the BGSET bulk entry is the penalty (PEN) factor, which is
used to adjust the stiffness of the glue condition. The default penalty factor is
sufficient for most cases, but can be adjusted if separation of the surfaces is
observed.
Examples have been provided in the install location
NX_Nastran_Install_Path/nxn4/nast/tpl to demonstrate capabilities and to
show the correct syntax for surfacetosurface gluing. These files will all start with
“glue” following with a solution number. For example, one of the files is
glue103.dat.
New BGSET Case Control Card
Selects the glue contact set.
Format:
BGSET=n
Examples:
BGSET=5
New BGSET Bulk Data Entry
Defines glued contact pairs of a 3D set.
Format:
BGSET Glue Contact Set Selection
Describers Meaning
n Glue contact set identification of a BGSET Bulk Data entry.
(Integer>0)
BGSET
3D Glue Contact Set Definition
1 2 3 4 5 6 7 8 9 10
BGSET GSID SID1 TID1 SDIST1 PEN
SID2 TID2 SDIST2
etc
41 CHAPTER 4
Miscellaneous Enhancements
Example:
Remarks:
1. The default search distance will glue all overlapping sections of the source and
target regions. This value can be used in special cases to control what subregions are
to be glued.
2. The default penalty factor will be sufficient for most cases. Increase it if separation
of the surfaces is observed. If defined too large, numerical problems may occur.
BGSET 4 1 2
4 3
Field Contents
GSID Glue set identification number. (Integer>0)
SIDi Source region identification number of glue pair i. (Integer > 0)
TIDi Target region identification number for glue pair i. (Integer > 0)
SDISTi Search distance for glue surfaces (Real);(Default= 100)
PEN Penalty value used in calculations. The value defined on the first line
will be used for all pairs. (Real);(Default = 1.0E5)
42
4.2 Improvements to AUTOMPC
In version 3 of NX Nastran, the Parameter AUTOMPC was introduced as an
automatic way of processing the dependent and independent degreeoffreedom
for rigid elements, constraint elements and MPC equations. Before AUTOMPC
was created, you were required to select independent and dependent degreeof
freedom when creating rigid elements, constraint elements and MPC equations.
This was a tedious process for models with large numbers of contraints.
In version 4.1, the following improvements have been made to AUTOMPC:
• Models with large numbers of MPC equations, particularily with large
numbers of RBE3 elements containing large numbers of grids, will see
performance improvements.
• When the AUTOMPC was originally created in version 3, an option was
created to specify that a dof (a dof which is included in an MPC
equation) must not be made part of the mset. This is done by including
a list of degreeoffreedom on USET/USET1 bulk data cards and making
them part of the U5 set. Now in version 4.1, an option to do the opposite
has been created. Including dof as part of the U4 set specifies they must
be made part of the mset.
An updated version of the AUTOMPC parameter is included below.
43 CHAPTER 4
Miscellaneous Enhancements
Updated Version of the AUTOMPC Parameter
AUTOMPC Default=NO
AUTOMPC=YES specifies that the software automatically selects
the mset dofs rather than use the mset values as specified on
MPC or RIGID element cards (RBE*, RBAR, RROD, etc.) in the
bulk data definition except as noted below.
This option relieves the need to carefully define rigid elements (or
MPCs) so as to not have a conflict of the msets between elements.
In addition, any redundant constraints will be eliminated.
This option is not available in some circumstances and will be
automatically set to NO for:
1) A pelement analysis with local coordinate systems or RSSCON
elements.
2) A design optimization solution (SOL=200) with DVGRID data.
The AUTOMPC option is recommended for use in models with
RSSCON elements connected to CPENTA elements.
If an RBE3 element contains UM information on the mset data,
those dofs will be used in the mset. SPOINTS in MPC equations
will always be made part of the mset.
When using this option, it is possible to specify that selected dof
must not be made part of the mset. This is accomplished by
defining these dofs on USET/USET1 bulk data cards making them
part of the U5 set. If specified, the UM information on RBE3
elements will be ignored.
An option also exists to specify that selected dof must be made
part of the mset. Again, using USET/USET1 bulk data cards, but
making them part of the U4 set.
44
4.3 Automatic Resubmitting of NX Nastran Jobs
When an NX Nastran job fails because of a failed license request, an option to have
the job retried automatically is now available. NX Nastran will now retry a failed
license request job every minute up to the value of the AUTHQUEUE keyword.
The default is 20 minutes.
45 CHAPTER 4
Miscellaneous Enhancements
4.4 Improvements to AUTOSPC
The Singular Value Decomposition (SVD) method is now available to AUTOSPC
unrestrained conditions in your model. The eigenvalue method is still used by
default, but SVD can be selected using the new system cell SVDSPC=1. The SVD
method is numerically more reliable and should be turned on in cases when you find
unexpected singularities remaining after the AUTOSPC operation.
System
Cell
Number
System Cell
Name
Function and Reference
419 SVDSPC Determines which AUTOSPC method is used.
0: Use the eigenvalue method (Default)
1: Use the Singular Value Decomposition
(SVD) method
46
MSC.Nastran 2001 Release Guide
APPENDIX
A
Upward Compatibility
■ DMAP Module Additions/Changes from NX Nastran 4.0 to 4.1
■ Datablock Additions/Changes from NX Nastran 4.0 to 4.1
48
A.1 DMAP Module Additions/Changes from NX Nastran
4.0 to 4.1
The following DMAP modules are additions or have changed in this release:
• GP4
• OFP
49 CHAPTER A
Upward Compatibility
Generates the degreeoffreedom set table based on single point constraints,
multipoint constraints, rigid elements, and set membership assignment Bulk Data
entries (e.g., ASET). Also generates the enforced displacement matrix, the multipoint
constraint equation matrix, and the enforced motion partitioning vector.
Format:
Input Data Blocks:
GP4 Generates the degreeoffreedom set table
GP4 CASECC,GEOM4,EQEXIN,SIL,GPDT,BGPDT,CSTM,
MEDGE,MFACE,MBODY,GEOM2,GDNTAB/
RMG,YS0,USET0,PARTV/
LUSET/S,N,NOMSET/S,N,MPCF2/S,N,NOSSET/S,N,NOOSET/
S,N,NORSET/S,N,NSKIP/S,N,REPEAT/S,N,NOSET/S,N,NOL/
S,N,NOA/SEID/ALTSHAPE/SEBULK/DMAPNO/AUTOMPC $
CASECC Table of Case Control command images.
GEOM4 Table of Bulk Data entry images related to constraints, degreeof
freedom membership and rigid element connectivity.
EQEXIN Equivalence table between external and internal grid/scalar
identification numbers.
SIL Scalar index list.
GPDT Grid point definition table.
BGPDT Basic grid point definition table.
CSTM Table of coordinate system transformation matrices.
MEDGE Edge table for pelement analysis.
MFACE Face table for pelement analysis.
MBODY Body table for pelement analysis.
GEOM2 Table of Bulk Data entry images related to element connectivity and
scalar points.
GDNTAB Table of grid points generated for pelement analysis.
50
Output Data Blocks:
Parameters:
RMG Multipoint constraint equation matrix.
YS0 Matrix of enforced displacements.
USET0 Degreeoffreedom set membership table for gset.
PARTV Partitioning vector of enforced motion dof.
LUSET Inputintegerdefault=0. The number of degreesoffreedom in the
gset.
NOMSET Outputintegerno default. Number of degreesoffreedom in the mset
or multipoint constraint and rigid element flag. Set to 1 if there are
none.
MPCF2 Outputintegerno default. Multipoint constraint set identification
number change flag. Set to 1 if the current subcase contains a different
multipoint constraint set from the previous subcase. Set to 1 otherwise
or if there are no multipoint constraints in the current subcase.
NOSSET Outputintegerno default. Number of degreesoffreedom in the sset.
or single point constraint flag. Set to 1 if there are none.
NOOSET Outputintegerno default. Number of degreesoffreedom in the oset
or omitted degreeoffreedom flag. Set to 1 if there are none.
NORSET Outputintegerno default. Number of degreesoffreedom in the rset.
or supported degreeoffreedom flag. Set to 1 if there are none.
NSKIP Input/outputintegerno default. The record number in CASECC
corresponding to the first subcase of the current boundary condition.
REPEAT Outputintegerno default. Last boundary condition flag. Set to 1 at
the last boundary condition; +1 otherwise.
NOSET Outputintegerno default. Constraint, omit, and support set flag. Set to
1 if NOMSET=1, NOSSET=1, NOOSET=1, NORSET=1 and no
degreesoffreedom defined in the aset (e.g., ASETi, QSETi Bulk Data
entries); +1 otherwise.
NOL Outputintegerdefault=1. Dependent set flag. Set to 1 if all degreesof
freedom belong to mset, sset, oset, and/or rset; otherwise, the
degreesoffreedom in the lset.
NOA Outputintegerdefault=1. Constraint and omit set flag. Set to 1 if
NOMSET=1, NOSSET=1, and NOOSET=1; otherwise the number of
degreesoffreedom in the aset.
SEID Inputintegerdefault=0. Superelement identification number.
51 CHAPTER A
Upward Compatibility
Remarks:
1. YS and PARTV will be purged if SPCD or SPC Bulk Data entries do not specify
nonzero values for displacement, velocity, or acceleration.
2. GEOM4 may be purged.
3. CSTM may be purged if no coordinate systems are used.
ALTSHAPE Inputintegerdefault=0. Specifies set of displacement functions in
pelement analysis. ALTSHAPE=0 selects the MacNeal set and 1 selects
the Full Product Space set.
SEBULK Inputlogicaldefault=FALSE. Partitioned superelement presence flag.
Set to TRUE if partitioned superelements are present or BEGIN SUPER
is specified for the first BEGIN BULK Case Control command.
DMAPNO Inputintegerdefault=0. DMAP solution number.
AUTOMPC Inputcharacterdefault=NO. Auto MPC processing flag.
52
To output (print or punch) data blocks prepared by other modules in useroriented,
selfexplanatory formats.
Format:
Input Data Blocks:
Output Data Blocks:
None.
Parameters:
OFP Output file processor
OFP OFP1,OFP2,OFP3,OFP4,OFP5,OFP6,
CSTM,BGPDTVU,ERROR1,DEQATN,DEQIND,DIT//
S,N,CARDNO/ODCODE/PVALID/DFLAG/VFLAG/AFLAG $
OFPi Output table suitable for processing by the OFP module. See Remark 2.
CSTM Table of coordinate system transformation matrices.
EHT Element hierarchical table for pelement analysis.
BGPDTVU Basic grid point definition table for a superelement and related to
geometry with viewgrids added.
ERROR1 Errorestimate table updated for current superelement or adaptivity
loop.
DEQATN Table of DEQATN Bulk Data entry images.
DEQIND Index table to DEQATN data block.
DIT Table of TABLEDi Bulk Data entry images.
CARDNO Input/outputintegerdefault=0. Punch file line counter. CARDNO is
incremented by one for each line written to the punch file and is also
written into columns 7380 of each line.
ODCODE Inputintegerdefault=1. Output device code override. See Remark 4.
ODCODE overrides the code stored in the DBi's according to the
following table:
ODCODE Output Directed to:
1 Print
2 Plot
3 Print and Plot
53 CHAPTER A
Upward Compatibility
Remarks:
1. Any or all data blocks may be purged.
2. DMAP modules READ (LAMA, OEIGS, LAMX, CLAMX), CEAD (CLAMA and
OCEIGS), and LAMX (LAMB) are matrix operation modules that prepare OFP
formatted data blocks. Modules SDR2, SDR3, VDR, VDRE, ADR, CURV,
DDRMM, DRMH3, ELFDR, GPFDR, GPWG, LAMX, MDATA, SDRCOMP,
SDRX, and SDRHT also prepare OFP formatted data blocks.
3. Parameter ODCODE is not honored by data blocks LAMA, OEIGS, LAMX,
CLAMA, and OGPWG, which are created by READ, CEAD, LAMX, and GPWG.
4. CSTM, EHT, BGPDTVU, and ERROR1 are required if pelements are specified
and only for data recovery; i.e., displacement, stress, strain, etc.
4 Punch
5 Print and Punch
6 Plot and Punch
7 Print, Plot, and
Punch
PVALID Inputintegerdefault=0. Pelement adaptivity loop identification
number.
DFLAG Inputintegerdefault=0. Displacement output flag.
= 0 output displacement “as is”
= 1 output displacement as “relative motion”
= 2 do not output displacement
VFLAG Inputintegerdefault=0. Velocity output flag.
= 0 output velocity “as is”
= 1 output velocity as “relative motion”
= 2 do not output velocity
AFLAG Inputintegerdefault=0. Acceleration output flag.
= 0 output acceleration “as is”
= 1 output acceleration as “relative motion”
= 2 do not output acceleration
54
5. CSTM, DEQATN, DEQIND, and DIT are required if the CORD3G Bulk Data
entry is present and only for element data recovery; i.e., displacement, stress,
strain, etc.
Example:
Print the OUG1 table from the SDR2 module:
OFP OUG1/ $
55 CHAPTER A
Upward Compatibility
A.2 Datablock Additions/Changes from NX Nastran 4.0
to 4.1
The following Datablocks are additions or have changed in this release:
• OCPSDF
56
Table of crosspower spectral density functions.
Record 0  HEADER
Record 1  IDENT
OCPSDF Table of crosspower spectral density functions.
Word Name Type Description
1 NAME(2) CHAR4 Block Name
Word Name Type Description
1 ACODE(C) I Device code + 10*Approach code
2 TCODE(C) I Table code; always 4100
3 UNDEF none
4 RANDID I RANDOM set identification number
5 CCODE I Device code +10*function number
6 RCROID I RCROSS identification number
7 UNDEF(2) none
9 OCODE I Output code (2=real, 3=complex)
10 NUMWDE(C) I Length of entries in RECORD=DATA
(always 3)
11 RTYPE1 CHAR4 Type of first response quantity
12 ID1 I Element, grid or scalar point ID
number
13 COMP1 I Component code (item) ID number
14 RTYPE2 CHAR4 Type of second response quantity
15 ID2 I Element, grid, or scalar point ID
number
16 COMP2 I Component code (item) ID number
17 CURID I Curve ID number
18 UNDEF(33) none
51 TITLE(32) CHAR4 Title
57 CHAPTER A
Upward Compatibility
Record 2  DATA
Record 3  TRAILER
Notes:
1. Records repeat for each subcase having any output requests. Words 13 in
record 2 repeat for each frequency. Records 1 and 2 repeat for each function
generated.
2. Device code:
1 = print
4 = punch
5 = print and punch
3. Approach code:
1 = statics
2 = reigen
3 = ds0
4 = ds1
5 = freq
83 SUBTITL(32) CHAR4 Subtitle
115 LABEL(32) CHAR4 Label
Word Name Type Description
1 FREQ RS Frequency (Hz)
2 RPSDF RS Real part of crosspower spectral density
function value
3 IPSDF RS Imaginary part of crosspower spectral
density function value
Word Name Type Description
1 WORD1 I Number of records
2 WORD2 I Number of data values in record 2.
3 UNDEF(5) none
Word Name Type Description
58
6 = bkl0
7 = bkl1
8 = ceigen
9 = pla
4. RTYPEi:
DISP = displacement
VELO = velocity
ACCE = acceleration
OLOA = applied loads
SPCF = singlepoint constraint force
MPCF = multipoint constraint force
STRE = stress
STRA = strain
FORC = force
MSC.Nastran 2001 Release Guide
APPENDIX
B
System Descriptions
■ Supported System Configurations for NX Nastran 4.1
60
B.1 Supported System Configurations for NX Nastran
4.1
System Description – HP9000 – HPUX
Item Description
Supported Model(s) PARISC
Configurations for
Installed Timing
Constants
250, 710, 712, 715, 720, 730, 735, 778, 800, 819, 889, 2200, 2600,
2733, 3700, 4000, 4900, 6750
Build Operating System PARISC: HPUX B.11.00
Other Supported
Operating Systems
HPUX B.11.11
Word Length 32 bits
Build Type LP64, LP64 DMP
System Description – Intel – Linux
Item Description
Supported Model(s) Intel and Intelcompatible
Configurations for
Installed Timing
Constants
P4 2.8Ghz
Build Operating System Red Hat 7.3
Other Supported
Operating Systems
Suse 9.2, Red Hat EL 3.0, Red Hat EL 4.0
Word Length 32 bits
Build Type ILP32, ILP32 DMP
61 CHAPTER B
System Descriptions
System Description – Intel – Windows (32bit)
Item Description
Supported Model(s) Intel and Intelcompatible
Configurations for
Installed Timing
Constants
Pentium II 400 MHz, P4 1.5GHz, Pentium Pro.
Build Operating System Windows 2000, SP3
Other Supported
Operating Systems
WXP SP1, WXP SP2, WXP64 (on EM64T/Opteron), Win 2003
Server (on EM64T/Opteron)
Word Length 32 bits
Build Type ILP32
System Description – IBM RS/6000 – AIX (64 bit)
Item Description
Supported Model(s) Power, Power2, Power3, Power4
Installed Timing
Constants
303,320H, 370, 375, 390, 397, 530, 530h, 550, 560, 570, 580, 590, 591,
950, 980, 990, 4316
Build Operating System AIX 5.1
Other Supported
Operating Systems
AIX 5.2, AIX 5.3
Word Length LP64: 32 bits; ILP64: 64 bits
Build Type LP64, LP64 DMP, ILP64, ILP64 DMP
System Description – SGI R8K, R10K, R12K – IRIX64
Item Description
Supported Model(s) R8K, R10K, R12K, R16K
Configurations for
Installed Timing
Constants
IP7, IP19, IP20, IP21, IP22, IP27, IP28, IP30, IP35, 240, 510
Build Operating System IRIX 6.5.7
62
Other Supported
Operating Systems
IRIX 6.5.21, IRIX 6.5.24m, IRIX 6.5.27m
Word Length 32 bits
Build Type LP64, LP64 DMP
System Description – Sun SPARC – Solaris
Item Description
Supported Model(s) UltraSPARC
Installed Timing
Constants
UltraSPARC (75 & 95)
Build Operating System UltraSPARC:Solaris 8
Other Supported
Operating Systems
Solaris 9, Solaris 10
Word Length 32 bits
Build Type LP64
System Description – SGI R8K, R10K, R12K – IRIX64
Item Description
System Description – X86_64 Linux (AMD Opteron/EM64T)
Item Description
Supported Model(s) X8664 Linux
Installed Timing
Constants
8664
Build Operating System SuSE 9.0
Other Supported
Operating Systems
Suse 9.1, Suse 9.3, Suse SLES9, Red Hat EL 3.0, Red Hat EL 4.0
Word Length LP64: 32 bits; ILP64: 64 bits
Build Type LP64, LP64 DMP, ILP64, ILP64 DMP
63 CHAPTER B
System Descriptions
System Description – Intel Itanium HPUX
Item Description
Supported Model(s) IntelItaniumHPUX
Installed Timing
Constants
4900, 5300, 5400
Build Operating System HPUX B.11.22
Other Supported
Operating Systems
HPUX B.11.23
Word Length LP64: 32 bits; ILP64: 64 bits
Build Type LP64, LP64 DMP, ILP64, ILP64 DMP
System Description – Intel Itanium Linux
Item Description
Supported Model(s) Itanium II
Installed Timing
Constants
IA64 800 Mhz & 733Mhz
Build Operating System Red Hat AW2.1
Other Supported
Operating Systems
Red Hat EL3.0, Red Hat EL4.0
Word Length LP64: 32 bits; ILP64: 64 bits
Build Type LP64, LP64 DMP, ILP64, ILP64 DMP
System Description – SGI Altix
Item Description
Supported Model(s) SGIALTIX
Installed Timing
Constants
6402
Build Operating System SGI ProPack 3 sp3
Other Supported
Operating Systems
SGI ProPack 4
64
Word Length LP64: 32 bits; ILP64: 64 bits
Build Type LP64, LP64 DMP, ILP64, ILP64 DMP
System Description – SGI Altix
Item Description
System Description – Intel (EM64T/Opteron) – Windows (64 bit)
Item Description
Supported Model(s) Intel and Intelcompatible
Configurations for
Installed Timing
Constants
Pentium II 400 MHz, 733 MHz Itanium 32 Bit, P4 1.5GHz,
Pentium Pro.
Build Operating System Windows 2003 Server
Other Supported
Operating Systems
WXP64
Word Length 32 bits
Build Type LP64
Proprietary & Restricted Rights Notice
2006 UGS Corp. All Rights Reserved. This software and related documentation are proprietary to
UGS Corp. LIMITATIONS TO U.S. GOVERNMENT RIGHTS. UNPUBLISHED  RIGHTS RESERVED UNDER THE COPYRIGHT LAWS OF THE UNITED STATES. This computer software and related computer software documentation have been developed exclusively at private expense and are provided subject to the following rights: If this computer software and computer software documentation qualify as “commercial items” (as that term is defined in FAR 2.101), their use, duplication, or disclosure by the U.S. Government is subject to the protections and restrictions as set forth in the UGS Corp. commercial license for the software and/or documentation as prescribed in FAR 12.212 and FAR 27.405(b)(2)(i) (for civilian agencies) and in DFARS 227.72021(a) and DFARS 227.72023(a) (for the Department of Defense).,or any successor or similar regulation, as applicable or as amended from time to time. If this computer software and computer documentation do not qualify as “commercial items,” then they are “restricted computer software,” and are provided with “restrictive rights,” and their use, duplication or disclosure by the U.S. Government is subject to the protections and restrictions as set forth in FAR 27.404(b) and FAR 5222714 (for civilian agencies), and DFARS 227.72035(c) and DFARS 252.2277014 (for the Department of Defense), or any successor or similar regulation as applicable or as amended from time to time. UGS Corp. , Suite 600  5800 Granite Parkway, Plano, Texas 75024. NASTRAN is a registered trademark of the National Aeronautics and Space Administration. NX Nastran is an enhanced proprietary version developed and maintained by UGS Corp. MSC is a registered trademark of MSC.Software Corporation. MSC.Nastran and MSC.Patran are trademarks of MSC.Software Corporation. All other trademarks are the property of their respective owners.
C O N T E N T S
NX Nastran Release Guide
NX Nastran Release Guide
1
Introduction
■
NX Nastran 4.1 Overview, 2
2
Dynamics
■
SPC/SPCD Enforced Motion, 6 ❑ Introduction, 6 ❑ Residual Vector Update, 6 ❑ Mathematical Details for Relative Displacement Formulation, 8 ❑ Updated DISPLACEMENT Bulk Data Entry, 9 ❑ Updated VELOCITY Bulk Data Entry, 11 ❑ Updated ACCELERATION Bulk Data Entry, 13 Random Response Analysis, 16 ❑ Introduction, 16 ❑ Theory for Crosspower Spectral Density and Crosscorrelation Functions, 17 ❑ New RCROSS Case Control Card, 19 ❑ New RCROSS Bulk Data Entry, 20
■
3
Advanced Nonlinear
■
Improvements to the Contact Algorithm, 24 ❑ Updated NXSTRAT Card, 25
4
Miscellaneous Enhancements
■
SurfacetoSurface Gluing, 38 ❑ Introduction, 38 ❑ Defining Glue Regions (BSURF, BCPROP and BSURFS Bulk Entries), 38 ❑ Defining Glue Pairs (New BGSET Case Control and Bulk Entry), 39 ❑ New BGSET Case Control Card, 40 ❑ New BGSET Bulk Data Entry, 40 Improvements to AUTOMPC, 42
■
❑ ■ ■ Updated Version of the AUTOMPC Parameter.1.1. 48 Datablock Additions/Changes from NX Nastran 4. 43 Automatic Resubmitting of NX Nastran Jobs.0 to 4.0 to 4. 44 Improvements to AUTOSPC.1. 55 B System Descriptions ■ Supported System Configurations for NX Nastran 4. 60 . 45 A Upward Compatibility ■ ■ DMAP Module Additions/Changes from NX Nastran 4.
Nastran 2001 Release Guide CHAPTER 1 Introduction ■ NX Nastran 4.MSC.1 Overview .
Dynamics. Introduction. Chapter 3. new output control options have been added to the DISPLACEMENT. Miscellaneous Enhancements.1 Overview This section presents a short overview of the features introduced in NX Nastran 4. and ACCELERATION case control entries to designate whether you want absolute (default) or relative output. This enhancement will eliminate the need for automatic residual vector generation (which was done in the 4. In addition to the relative motion calculation. .1 NX Nastran 4. Features related to dynamic analysis have been implemented in this release. These features are summarized below: • SPC/SPCD Enforced Motion. This chapter describes new enhancements as related to solutions 601 and 701: • Improvements to the contact algorithm. • Random Response Analysis. Chapter 2. Chapter 4. A new option to “glue” element faces together during a solution is available in this release of NX Nastran. Advanced Nonlinear. Chapter 1. The current SPC/SPCD enforced motion capability has been enhanced to replace the current “absolute” displacement formulation with a “relative” displacement formulation. This chapter summarizes other useful enhancements that do not fit into the previously mentioned categories and covers the following topics: • SurfacetoSurface Gluing.1. The contact algorithm used in SOL 601 and 701 has been updated with a new contact segment option. VELOCITY.1. The new RCROSS case control and bulk data commands are now available for requesting CrossPower Spectral Density output. Gives an overview of new features in NX Nastran 4. the order of the segments created will match the order of the elements thus improving the output of contact results. Specifically.0 release).2 1.
or not be included in the mset.0 to NX Nastran 4. to be part of the mset.CHAPTER 1 Introduction 3 • Improvements to AUTOMPC. System Descriptions. Upward Compatibility. This section contains the DMAP and Datablock changes from NX Nastran 4. • New AUTOSPC method is available. The SVD method is numerically more reliable and should be turned on in cases when you find unexpected singularities remaining after the AUTOSPC operation. which is included in an MPC equation. You can now force a dof to be included. The new AUTOSPC method Singular Value Decomposition (SVD) is now available. .1. • Automatic Resubmitting of NX Nastran Jobs. The eigenvalue method is the default. The best performance improvements are seen with models containing large numbers of MPC equations. Appendix A. This section contains a list of the system configurations which NX Nastran supports for this release. but SVD can be selected by including the new system cell SVDSPC=1. a new option is available to force a degreeoffreedom (dof). A new option is available to automatically resubmit jobs which fail to run because of a failed license request. Also. Performance improvements have been made to the AUTOMPC capability introduced in NX Nastran 3. The program will retry the job every minute up to the value of the new AUTHQUEUE keyword. Appendix B.
4 .
Nastran 2001 Release Guide CHAPTER 2 Dynamics ■ SPC/SPCD Enforced Motion ■ Random Response Analysis .MSC.
and ACCELERATION case control entries. The updated DISPLACEMENT. there was a change to make residual vector generation happen automatically when there was enforced motion present. VELOCITY.YES and PARAM.YES if you want residual vector creation to occur. and you are required to use PARAM. the enforced motion results are of good quality without the addition of residual vector generation. With the new relative displacement formulation in release 4. particularily when damping is included. With the new relative approach. for example. thus the SPC/SPCD method may now be considered as the enforced motion method of choice.RESVEC. thus eliminating the need to employ large mass or Lagrange Multipliers. Though it is a more straightforward method as compared to the large mass method of enforced motion.1 SPC/SPCD Enforced Motion Introduction The SPC/SPCD method of enforced motion allows the direct specification of displacements. the new describers ABS/REL have been added to the DISPLACEMENT. They are also supported on a subcase level to allow for different output requests in different subcases. Residual Vector Update In NX Nastran version 4. In addition to the formulation change. RESVINER. To correct these problems. and ACCELERATION case control entries are included at the end of this section.0. As the name implies. it is now based on a relative motion approach versus the absolute motion approach. VELOCITY. the current SPC/SPCD method using the absolute displacement formulation has shown to give poor results under certain circumstances. This was done to improve enforced motion results. Having these options on each entry allows you the flexibility to request. the issues associated with the SPC/SPCD method have been resolved.6 2. velocities. a new “relative” displacement formulation has been introduced in this release to replace the current “absolute” displacement formulation. Residual vector generation is no longer automatic in this release. Below are the updated parameters showing their new defaults: . relative displacement output with absolute acceleration output in the same run.1. or accelerations via SPC/SPC1/SPCD data.
YES. • unit loads.) By default. Reorthogonalize static shapes with mode shapes. Augment static shapes due to inertial loads (unit acceleration of mass). .U6 entries at the desired dofs and PARAM. you will need to supply SUPORTi entries.RESVEC.RESVEC. RESVSO YES RESVSE RESVSLI RESVINER NO YES Default=NO (Default = NO for SOL 111 & 112 when enforced motion is present.YES.) See related parameter RESVEC. If the stiffness is wellconditioned.YES.RESVINER. If you want residual vectors due to: • applied loads (LOAD or LOADSET Case Control commands) then specify PARAM. Print strain energy of the static shapes. • inertial loads (unit acceleration of mass) then specify PARAM. If the model is unrestrained. Remove linearly dependent shapes. residual vectors are not computed. Related parameters are: PARAM name RESVEC RESVINER Default Value NO NO Description Augment static shapes due to applied loads. then specify USETi.CHAPTER 2 Dynamics 7 RESVEC Default=NO (Default updated to NO for SOL 111 & 112 when enforced motion is present. this is not required.
although this term will not have a large impact since the damping is usually specified in terms of modal diagonal damping.K = mass.8 Mathematical Details for Relative Displacement Formulation The SPC/SPCD enforced motion formulation uses an absolute displacement formulation per the equation: ·· · ·· · M ff u f + C ff u f + K ff u f = P f – ( M fs u s + C fs u s + K fs u s ) where: M. 1 1 u s = applied enforced motion – C ff K ff K fs + C fs 1 .C. The absolute displacement formulation equation will be replaced by the more accurate enforced motion equations: 1 1 ·· · ·· · M ff y f + C ff y f + K ff y f = P f – ( – M ff K ff K fs + M fs )u s – ( – C ff K ff K fs + C fs )u s u f = y f – K ff K fs u s where y f = relative displacement of the fset dof. and stiffness matrices u f = absolute displacements of the fset dof P f = loads applied to the fset dof · The damping loading term C fs u s is not included. damping. Using the two equations above requires that the residual vector be computed from the term: – M ff K ff K fs + M fs If there is discrete damping present. an additional residual vector will be computed from the term: 1 · The damping loading term ( – C ff K ff K fs + C fs )u s will also be included.
PRINT. Output will be presented as a tabular listing of load. PUNCH .CHAPTER 2 Dynamics 9 Updated DISPLACEMENT Bulk Data Entry DISPLACEMENT Displacement Output Request Requests the form and type of displacement or pressure vector output. Phase output is in degrees. Requests polar format (magnitude and phase) of complex output. displacement results will be output as absolute displacement. frequency. Note: PRESSURE and VECTOR are equivalent commands. REAL)=ALL Describers SORT1 Meaning Output will be presented as a tabular listing of grid points for each load. depending on the solution sequence. ATOC REL SORT2 PLOT PHASE RALL ALL = n NONE Examples: DISPLACEMENT=5 DISPLACEMENT(REAL)=ALL DISPLACEMENT(SORT2. or time. SORT2 PRINT PUNCH PLOT REAL or IMAG PHASE ABS . frequency or time for each grid point. REAL or IMAG . Use of either REAL or IMAG yields the same output. For enforced motion dynamic analysis. but does not print. Generates. The punch file will be the output medium. Format: ABS PSDF DISPLACEMENT SORT1 . displacement data. The printer will be the output medium. eigenvalue. PUNCH. Requests rectangular format (real and imaginary) of complex output.
and VELO then the remaining commands will also be output in SORT2 format. ENTH. STRE. 2. The request must be made above the subcase level and RANDOM must be selected in the Case Control. displacement results will be output relative to the enforced motion input. and buckling analysis. Requests that power spectral density function and the autocorrelation function be calculated for random analysis postprocessing. OLOA. real and complex eigenvalue analysis. then the remaining commands will also be output in SORT1 format. DISP. STRE. requests. FORC. Requests the power spectral density function be calculated for random analysis postprocessing. The type of analysis determines which “SORT” is the default: • SORT1 is the default in static analysis. OLOA. flutter analysis. SPCF.10 Describers REL PSDF Meaning For enforced motion dynamic analysis. SPCF. MPCF. frequency response. • SORT2 is the default in transient response analysis (structural and heat transfer). (Integer>0) ATOC RALL ALL NONE n Remarks: 1. SORT2 is not available for real eigenvalue (including buckling). If SORT1 is selected in a transient solution for one or more of the commands ACCE. See Remark 8. FORC. HDOT. complex eigenvalue. The request must be made above the subcase level and RANDOM must be selected in the Case Control. STRA. Displacements for all points will be output. • XY plot requests will force SORT2 format overriding SORT1 format . Displacement for no points will be output. Set identification of a previously appearing SET command. The request must be made above the subcase level and RANDOM must be selected in the Case Control. DISP. Requests the autocorrelation function be calculated for random analysis postprocessing. If SORT2 is selected in a frequency response solution for one or more of the commands ACCE. See Remark 8. MPCF. Both PRINT and PUNCH may be requested. See Remark 8. Only displacements of points with identification numbers that appear on this SET command will be output. steady state heat transfer analysis. and VELO. STRA. or flutter analysis.
Remarks related to SOLs 601 and 701: 1. Displacements. . The units of translation are the same as the units of length of the model. Format: SORT1 PRINT. 2. 8. Updated VELOCITY Bulk Data Entry VELOCITY Velocity Output Request Requests the form and type of velocity vector output. Output requested for set n in this command will be combined with the sets requested in the VELOCITY and ACCELERATION commands. The PLOT option is used when curve plots are desired in the magnitude/phase representation and no printer output request is present for magnitude/phase representation. and displacements will be output at the grid points of the combined set. . PUNCH REAL or IMAG ABS PSDF . Rotations are in units of radians. Displacement results are output in the global coordinate system (see field CD on the GRID Bulk Data entry). 7.f06. . They provide no output to the . 4. PHASE. IMAG. 6. ATOC. and RALL options are for future support of random analysis postprocessing. 5. velocities and accelerations must be output for the same set of grid points if requested. The PSDF. DISPLACEMENT=NONE overrides an overall output request. Output is restricted to REAL format. ATOC and RALL are ignored. ATOC VELOCITY REL SORT2 PLOT PHASE RALL ALL = n NONE Examples: . PSDF.CHAPTER 2 Dynamics 11 3. VECTOR and PRESSURE are alternate forms and are entirely equivalent to DISPLACEMENT.
Velocity for all solution points will be output.PUNCH)=ALL Describers SORT1 Meaning Output will be presented as a tabular listing of grid points for each load. velocity results will be output as absolute velocity. Requests polar format (magnitude and phase) of complex output. The punch file will be the output medium. velocities. Requests the power spectral density function be calculated and stored in the database for random analysis postprocessing. depending on the solution sequence. Generates.12 VELOCITY=5 VELOCITY(SORT2. The request must be made above the subcase level and RANDOM must be selected in the Case Control. Use of either REAL or IMAG yields the same output.PHASE. or time. Set identification of a previously appearing SET command. but does not print. For enforced motion dynamic analysis. Requests that both the power spectral density function and the autocorrelation function be calculated and stored in the database for random analysis postprocessing. For enforced motion dynamic analysis. Output will be presented as a tabular listing of frequency or time for each grid point. Phase output is in degrees. velocity results will be output relative to the enforced motion input. The request must be made above the subcase level and RANDOM must be selected in the Case Control. Requests the autocorrelation function be calculated and stored in the database for random analysis postprocessing. Requests rectangular format (real and imaginary) of complex output. (Integer>0) SORT2 PRINT PUNCH PLOT REAL or IMAG PHASE ABS REL PSDF ATOC RALL ALL NONE n . The printer will be the output medium. The request must be made above the subcase level and RANDOM must be selected in the Case Control. frequency. Only velocities of points with identification numbers that appear on this SET command will be output. eigenvalue. Velocity for no solution points will be output.
2. 3. Updated ACCELERATION Bulk Data Entry ACCELERATION Acceleration Output Request Requests form and type of acceleration vector output. PHASE. Format: PSDF ABS . Output requested for set n in this command will be combined with the sets requested in the DISPLACEMENT and ACCELERATION commands. and RALL options are for future support of random analysis postprocessing. ATOC ACCELERATION SORT1 . 2. Displacements. 6. Velocity output is only available for transient and frequency response problems. They provide no output to the . The PLOT option is used when curve plots are desired in the magnitude/phase representation and no printer request is present for the magnitude/phase representation. VELOCITY=NONE overrides an overall output request. Output is restricted to REAL format. PRINT. 4. PSDF. Both PRINT and PUNCH may be requested. Remarks related to SOLs 601 and 701: 1. PUNCH . 5. The PSDF. ATOC.CHAPTER 2 Dynamics 13 Remarks: 1. IMAG. 7. See Remark 2 under “DISPLACEMENT” on page 9 for a discussion of SORT1 and SORT2. velocities and accelerations must be output for the same set of grid points if requested. REAL or IMAG . REL SORT2 PLOT PHASE RALL ALL = n NONE Examples: . Velocity results are output in the global coordinate system (see field CD on the GRID Bulk Data entry). and velocities will be output at the grid points of the combined set.f06. ATOC and RALL are ignored.
Request both the power spectral density function and autocorrelation function be calculated for random analysis postprocessing. Requests the power spectral density function be calculated for random analysis postprocessing. Computes. Use of either REAL or IMAG yields the same output. acceleration results will be output relative to the enforced motion input. PUNCH. The punch file will be the output medium. The printer will be the output medium. Only accelerations of points with identification numbers that appear on this SET command will be output. For enforced motion dynamic analysis. depending on the solution sequence. The request must be made above the subcase level and RANDOM must be selected in the Case Control. (Integer>0) SORT2 PRINT PUNCH PLOT REAL or IMAG PHASE ABS REL PSDF ATOC RALL ALL NONE n . For enforced motion dynamic analysis. Requests polar format (magnitude and phase) of complex output. but does not print or punch. or time. Output will be presented as a tabular listing of frequency or time for each grid point. Requests the autocorrelation function be calculated for random analysis postprocessing. PHASE)=ALL ACCELERATION(SORT1. PRINT. Set identification of a previously appearing SET command. Requests rectangular format (real and imaginary) of complex output. Accelerations at all points will be output. The request must be made above the subcase level and RANDOM must be selected in the Case Control. frequency. acceleration output. eigenvalue. PHASE)=17 Describers SORT1 Meaning Output will be presented as a tabular listing of grid points for each load. The request must be made above the subcase level and RANDOM must be selected in the Case Control.14 ACCELERATION=5 ACCELERATION(SORT2. acceleration results will be output as absolute acceleration. Accelerations at no points will be output. Phase output is in degrees.
and RALL options are for future support of random analysis postprocessing. 6.f06. Both PRINT and PUNCH may be requested.CHAPTER 2 Dynamics 15 Remarks: 1. ATOC and RALL are ignored. They provide no output to the . The PSDF. 4. See Remark 2 under “DISPLACEMENT” on page 9 for a discussion of SORT1 and SORT2. PSDF. 2. 3. PHASE. Remarks related to SOLs 601 and 701: Output is restricted to REAL format. The PLOT option is used when curve plots are desired in the magnitude/phase representation and no printer request is present for magnitude/phase representation. 5. Acceleration results are output in the global coordinate system (see field CD on the GRID Bulk Data entry). IMAG. Acceleration output is only available for transient and frequency response problems. 7. ACCELERATION=NONE allows overriding an overall output request. . ATOC.
1. and earthquake ground motions. Formats of these entries are in included at the end of this section. Note that although the process is described as two steps. wind loads on buildings. NX Nastran has the capability for performing random analysis.0. The procedure is a twostep process in which first a frequency response analysis is performed to calculate transfer functions which are the ratio of output to a unit input. the loading on a structure is not known in a definite (or deterministic) sense. If the two variables are the same. It should be expected that the response of the structure due to random loads will also be random in nature and analysis methods that determine the statistical properties of response are appropriate. Now with NX Nastran 4. ocean wave loads on offshore platforms. The input PSD functions represent the statistics of the applied loads. Examples of random loads include: rough road surface loads on automobiles. If there are several applied loads and they are uncorrelated from each other. If on the other hand the loads are not independent of each other. In the second step. only auto spectrum PSD functions of response could be output for random results. A PSD function describes how the variance of a time series of the product of two variables is distributed with frequency. . Up until the release of NX Nastran version 4. and instead is quantified in a statistical sense with properties such as the mean load and standard deviation of load. only the auto spectra of the loads need be applied. the PSD function is known as an auto spectrum. the PSD function is called a cross spectrum. and RMS (rootmeansquare) values of response.2 Random Response Analysis Introduction In many applications.16 2. RCROSS have been created for this purpose. the PSD loading function is used to scale the transfer functions to compute the random PSD response. Users were required to use DMAP methods if they were interested in obtaining cross spectrum results. A new Case Control command. number of zero crossings with positive slope per unit time. Such loadings are known as random or stochastic loads. it can be performed with NX Nastran as only one solution submittal. RCROSS and Bulk Data entry. if the variables are different. it is possible to request cross spectrum output using standard PSD solutions. Random response output consists of the response PSD. the cross spectrum of the loads need also be input to define the correlation of the loadings. vibration loads from rocket engines. autocorrelation functions. The most commonly used approach for random analysis uses Power Spectral Density (PSD) functions to define loading and the calculated response.
T ) = T – iwt we can define the crosspower spectral density (crossPSD) as lim 2 * . strain. rcross02. Simply stated. If we denote the Fourier transform of a time history as U a ( ω. the crossPSD is the product of the Fourier transform of two records.CHAPTER 2 Dynamics 17 The following examples have been provided in the install location NX_Nastran_Install_Path/nxn4/nast/tpl to demonstrate capabilities and to show the correct syntax for using the new RCROSS commands: rcross01.U a ( ω.T ) U b ( ω. It can be shown using equations (1) and (2) that the cross correlation function and cross spectrum are related as Fourier transform pairs given as S ab ( ω ) = 2 ∫ ∞ ∞ ∫0 u a ( t )e dt (2) R ab ( τ )e – iωt dτ (4) iωt 1 ∞ R ab ( τ ) = .T ) (3) S ab ( ω ) = T → ∞T where ω is angular frequency in rad/sec and the symbol (*) denotes complex conjugate.dat. The assumption of ergodicty means that as the length of the record is increased the average approaches the corresponding ensemble averages.u ( t )u b ( t – τ )dt R ab ( τ ) = (1) T → ∞ T ∫0 a where ua(t) and ub(t) can be displacement. rcross04. velocity. it can be shown to possess the following properties: R ab ( – τ ) = R ba ( τ ) (6) .∫ S ab ( ω )e dω (5) 4π ∞ It is noted that the cross correlation function is always real valued and the cross spectrum function is in general complex valued.dat. and force components in the same or different elements. the cross correlation function between a pair of time records ua(t) and ub(t) is defined as lim 1 T . rcross03.dat. The operation of integration over a time record of length T and dividing that quantity by T represents an averaging process over time. or stress. acceleration or singlepoint constraint force responses at the same or different grid points. Theory for Crosspower Spectral Density and Crosscorrelation Functions Assuming that a random process is ergodic.dat. In addition.
only a single response. For autocorrelation functions the mean crossproduct is known as the variance and its square root is the standard deviation. As evidenced by equation (1) it represents the mean cross product. if the standard deviation of response ua(t) is determined to be σ a . In many situations. . By using the standard assumption that loadings and response are Gaussian (normally distributed). we can rewrite S ab ( ω ) in terms of its real and imaginary parts as S ab ( ω ) = S ab ( ω ) + iS ab ( ω ) r i (8) r From the properties in equation (5) it can be determined that S ab ( ω ) is an even i function of ω and S ab ( ω ) is an odd function of ω . the likelihood that at any time the response is less than 3σ a is 99. knowing the covariance allows you to define the probability distribution and thus determine likelihood of occurrence of response levels.∫ S ab ( ω )dω = u a ( t )u b ( t ) 2π 0 where ( ) denotes mean average. Substituting equation (8) into the equation (7) and recalling that iωt e = cos ( ωt ) + i sin ( ωt ) . In that case. are computed. autocorrelation functions. rather than the joint response is of interest.9%.∫ [ S ab ( ω ) cos ( ωτ ) – S ab ( ω ) sin ( ωτ ) ]dω 2π 0 (9) A particular case of interest is the value of the crosscorrelation function for τ = 0 . and autospectrum functions. Using equation (9) it can be computed as 1 ∞ r R ab ( 0 ) = . The autospectrum by definition is completely real. S aa ( ω ) . Returning to the more general case. For crosscorrelation functions. R aa ( τ ) .18 S ab ( – ω ) = S ba ( ω ) = S ab ( ω ) * (7) It should also be noted that we have been referring to the general case where ua(t) and ub(t) are different responses. For example. ( 10 ) The mean cross product is an important statistical quantity. it can be shown that i 1 ∞ r R ab ( τ ) = . is it known as the covariance.
Format: REAL or IMAG PRINT RCROSS .CHAPTER 2 Dynamics 19 If a system is subject to multiple sources of excitation. Writes output to print file. (Default) PHASE PRINT .. Use of either REAL or IMAG yields the same output. [ PSDF ] PHASE NOPRINT Examples: RCROSS(PHASE) = 10 RCROSS(PSDF. (Default) Requests polar format (magnitude and phase) of complex output (for crosspower spectral density function).. . H aj ( ω ) is the frequency response function of ua(t) corresponding to the excitation source Pj(t) and similarly * H bk ( ω ) is the complex conjugate of the frequency response function of ub(t) corresponding to the excitation source Pk(t). we have S jk ( ω ) = 0 . [ PUNCH ]. the crossPSD of responses ua(t) and ub(t) is related to the crossPSDs of the excitation sources and the frequency response functions by the equation S ab ( ω ) = ∑ ∑ H aj ( ω )H bk ( ω )S jk ( ω ) j k * (11) where S jk ( ω ) is the crossPSD of loadings Pj(t) and Pk(t).NOPRINT. Phase output is in degrees.PUNCH) = 20 RCROSS = 30 Describers REAL or IMAG Meaning = n Requests rectangular format (real and imaginary) of complex output (for crosspower spectral density function). If the two excitation sources are not correlated. New RCROSS Case Control Card RCROSS CrossPower Spectral Density Functions Output Request Requests computation and output of crosspower spectral density functions in random analysis.
Format: 1 RCROSS 2 SID 3 RTYPE1 4 ID1 5 6 7 ID2 8 9 10 COMP1 RTYPE2 COMP2 CURID Example: RCROSS 20 DISP 50 2 STRESS 150 8 4 . 2. must be requested by corresponding case control entries in order to compute crosspower spectral density between the two response quantities specified by the RCROSS bulk data entry. Response quantities. and FORCE. Requests the crosspower spectral density function be calculated and output for random analysis postprocessing. STRESS. See remarks under the RANDOM case control entry. Writes output to punch file. 3. It is recommended that the DISPLACEMENT.20 Describers NOPRINT PUNCH PSDF Meaning Does not write output to the print file. and FORCE requests be put above the subcase level to ensure that these response quantities exist when the random analysis postprocessing occurs. STRESS. New RCROSS Bulk Data Entry RCROSS CrossPower Spectral Density Functions Output Defines a pair of response quantities for computing the crosspower spectral density functions in random analysis. (Integer >0) n Remarks: 1. (Default) Identification number of RCROSS bulk data entry to be used in random analysis. such as DISPLACEMENT. The case control RCROSS entry must be used in conjuction with the case control RANDOM entry. The response quantities must belong to the same superelement. The crosspower spectral density functions between two responses that belong to different superelements are not supported.
ID1. fields RTYPE2.CHAPTER 2 Dynamics 21 Field SID Contents Case control RCROSS identification number for crosspower spectral density function. See remark 2. (Character or blank) IDi COMPi CURID Element. and COMP2 represent the second response quantity. Fields RTYPE1. (Integer > 0) Curve identification number. and COMP1 represent the first response quantity. See remark 3. or scalar point identification number. At least one field must be selected. See remark 4. then the blank field takes the default from the defined field. . (Integer>0) RTYPEi Type of response quantity. (Integer > 0) Component code (item) identification number. The keywords for field RTYPEi are listed as follows: Keyword DISP VELO ACCEL OLOAD SPCF MPCF STRESS STRAIN FORCE Meaning Displacement Vector Velocity Vector Acceleration Vector Applied Load Vector Singlepoint Constraint Force Vector Multipoint Constraint Force Vector Element Stress Element Strain Element Force If either RTYPE1 or RTYPE2 is blank. This entry is required for computing the crosspower spectral density function. ID2. (Integer > 0 or blank) Remarks: 1. SID must be selected with the case control command (RCROSS=SID). grid. 2.
the item code is one of 1.5. . It is for your convenience to identify the output by using a single index. T2. the code of the real part must be selected. and 6. T3. always use 1. strain or force and is described in Tables “Element StressStrain Item Codes” and “Element Force Item Codes”. and R3. which represent the mnemonics T1. For grid points.22 3. R2. 4.3. R1. respectively. Field CURID is optional.2. For elements. For scalar points. the item code COMPi represents a component of the element stress. For an item having both a real and imaginary part.4.
Nastran 2001 Release Guide CHAPTER 3 Advanced Nonlinear ■ Improvements to the Contact Algorithm .MSC.
0 in BCTPARA • Only singlesided contact (default) is allowed. When quadratic contact segments are created on quadratic elements.1 when CSTYPE=1 is used. i. FRICMOD=0 or 1 in BCTPARA • No tied contact (default). i.. expecially when used with quadratic elements (for example..Use the new type of contact segment. listed below. i. will be eliminated in future releases. • Only constraint function algorithm (default) may be used.. 1 . TIED=0 in BCTPARA • Consistent contact stiffness cannot be used. Specifically. Note that the default settings comply with the restrictions.e. CSTYPE=1 is more accurate and will give better contact traction results.e. Default = 0) 0 . NSIDE=1 in BCTPARA • Only frictionless contact (default) or regular Coulomb friction is allowed. certain restrictions apply in NX Nastran 4. A new contact segment option is available for SOL 601 in NX Nastran 4. the resulting contact tractions are significantly better. i.. TYPE=0 in BCTPARA • Contact surface offset must be zero (default). These contact segments are created on the shell and solid element faces. contact segments are created during the solution in the regions where contact has been defined. i.e. the order of the segments created (linear or quadratic) will match the order of the elements.1 Improvements to the Contact Algorithm When contact definitions exist in an Advanced Nonlinear Solution (SOLs 601 and 701).24 3.. These restrictions. The new parameter CSTYPE has been created on the bulk data entry NXSTRAT to support the new contact segment creation. CSTIFF=0 in BCTPARA • Continuous normal must be used (default). (Integer.e. i.Use the old type of contact segment.e. OFFSET=0.1 that gives improved contact results. CSTYPE Selects the type of contact segment to use.. SEGNORM=0 or 1 in BCTPARA .e. However.. i. 10grid tetrahedral elements).e.
INIPENE=0 or 1 in BCTPARA Updated NXSTRAT Card (This includes a change to the param LSEARCH which is not specifically related to the contact output improvements. See remark 1 for parameters applicable to SOL 701.. Allowable names are given in Table 81. Format: 1 NXSTRAT 2 ID Param4 3 Param1 Value4 4 Value1 Param5 5 Param2 Value5 6 Value2 etc 7 Param3 8 Value3 9 10 Example: NXSTRAT 1 ATSNEXT AUTO 3 1 MAXITE 30 RTOL 0.CHAPTER 3 Advanced Nonlinear 25 • Initial penetration cannot be ignored (default). Currently not used. (Real or integer) VALUEi . (Character) Value of the parameter.005 Field ID PARAMi Contents Identification number.) NXSTRAT Strategy Parameters for SOLs 601 and 701 Defines parameters for solution control and strategy in advanced nonlinear structural analysis. i.e. (Integer > 0) Name of the NXSTRAT parameter. See Table 81.
Default = 1) 0 – Lumped mass is used 1 – Consistent mass is used Analysis Options TINT* Integration order for the local tdirection (through thickness) of shell elements with elastoplastic materials. 5point NewtonCotes is used for singlelayered shell and 3point NewtonCotes is used for multilayered shell. Note that 2point Gauss integration is always used for all shell elements with elastic materials. Default =1 for SOL 601 and 0 for SOL 701) 0 .26 Table 81 NXSTRAT Parameters Name Description Analysis Control Parameters SOLVER Selects the solver to use. 1 < TINT < 6 – Gauss integration method with integration order TINT 3. By default. Default = 0). Default = 0) 0 – No automatic incrementation scheme is used 1 – Automatic time stepping (ATS) scheme is enabled 2 – Automatic loaddisplacement control (LDC) scheme is enabled Indicates whether analysis continues when the system matrix is not positive definite. (Integer. (Integer. i. (Integer.e. Selects the type of mass matrix to be used in dynamic analysis. 7 – NewtonCotes integration with order TINT ICMODE* Indicates whether incompatible modes are used for 4node shell elements. (Integer. 5. AUTO=1 or AUTO=2 contact analysis is being performed It is not recommended to set NPOSIT=1 for a linear analysis. (Integer. analysis stops unless the ATS or LDC scheme is enabled. Default = 0) 0 – Direct sparse solver 1 – Multigrid solver Indicates whether automatic incrementation scheme is enabled. Default = 0) 0 – Analysis may stop 1 – Analysis continues Notes: If NPOSIT=0.Incompatible modes are used AUTO NPOSIT MASSTYP .Incompatible modes are not used 1 . (Integer.
Default = 0) 0 – Matrix stabilization is not used 1 – Matrix stabilization is used Matrix stabilization factor. (Integer. Note that u/p formulation is always used for hyperelastic elements and always not used for hyperfoam elements and elastic elements with Poisson’s ratio less than 0.0) Indicates whether u/p formulation is used for elements. its contribution to the overall stiffness of the structure is removed. Otherwise. This may help in the convergence of the solution. Updated LagrangianHencky (ULH) formulation is used. 1 – Use ULH formulation 2 – Use ULJ formulation Note: For shell elements which are not 4noded. For 3D solid.0. In restarting from SOL 601 to 701 or vice versa.CHAPTER 3 Advanced Nonlinear 27 Name MSTAB Description Indicates whether the stiffness matrix stabilization feature is used. ULH formulation is always used for large strains. the ULJ formulation is always used for large strains. the contribution from the element stiffness is gradually reduced to zero over time DTDELAY instead of being suddenly removed.48. By specifying DTDELAY > 0. (Real. plane strain and axisymmetric elements. ULFORM* . (Integer.0) When an element is too deformed and becomes “dead”. ULFORM needs to be specified such that both analyses use the same formulation. Default = 0) 0 – u/p formulation is not used 1 – u/p formulation is used instead of displacementbased formulation Indicates which large strain formulation is used for 4node shell elements. It is also not used for gasket elements (Integer. Default = 0) 0 – Updated LagrangianJaumann (ULJ) formulation is used if rigidtarget algorithm contact is used or SOL 701 is run. (Real. (Real. Default = 1. Default = 0. MSFAC DTDELAY* SDOFANG* UPFORM* Angle used to determine whether a shell midsurface node is assigned 5 or 6 degrees of freedom. Default = 5.0E12) Element death time delay.
Default = 1) The critical time step size is calculated based on certain assumptions. This parameter specifies that the critical time step size be recalculated every XDTCAL time steps. (Integer > 0. PARAM. i.0. 1 .28 Name DISPOPT Description Indicates whether prescribed displacements are applied to the original configuration or the deformed configuration. XDTCALo Calculation of the critical time step size may be computationally expensive. the direction and magnitude of the load may change due to large deformation of the structure.e.Time step size is calucated by the program based on the critical time step size.5) SOL 701 Time Stepping Selects time step method used in an explicit time integration analysis. Default = 0. to use a time step size smaller than the calculated critical time step size. (Real. (Integer. Default = 0. (Real. (Integer. Default = 0) 0 – Applied to original configuration 1 – Applied to deformed configuration Indicates whether prescribed loads (pressure and centrifugal) are deformationdependent. especially for nonlinear analysis. It is often necessary. Default = 0) 0 .25) Delta coefficient for the Newmark method.e. This option is only applicable for a restart analysis or when a delay (or arrival) time is specified for the prescribed displacement. The factor multiplied by the calculated critical time step size gives the time step size used in the analysis.LGDISP. Default = 1) 0 – Load is independent of structural deformation 1 – Load is affected by structural deformation Time Integration LOADOPT* ALPHA DELTA XSTEPo Alpha coefficient for the Newmark time integration method.9) XDTFACo . Default = 0.0 > Real > 0.1 (Integer. The data in the selected TSTEP bulk data entry is used to calculate the total solution time for the analysis. This option is only applicable for large displacement analysis. (4.The number of time steps and the time step size as specified in the selected TSTEP bulk data entry is used. i.
0) Multigrid Solver XDTMIN1o XDTMIN2o ITEMAX EPSIA EPSIB EPSII Maximum number of iterations allowed for the multigrid solver to converge. (Real = 1. (Real.0 < Real < 1. (0. If the critical time step size for an element is smaller than XDTMIN2. The amount of mass scaling is calculated for each element so that the critical time step size is equal to DTMIN1.0) The minimum time step size used to determine whether an element will be removed in an explicit time integration analysis.0) LSLOWER LSUPPER . Default = 0) 0 – Line search is not used 1 – Line search is used Lower bound for line search. See Remark 2 and warning in Remark 3. (Real.0.001) Upper bound for line search. the smaller will the critical time step size be. Default = 0. Default = 1. (1. Default = 1. (Real = 0. In explicit time integration. See warning in Remark 2. (Integer > 0. Default = 1000) Convergence tolerance EPSIA. Default = 0.0.CHAPTER 3 Advanced Nonlinear 29 Name XMSCALEo Description Specifies the factor to scale the mass (densities) of the entire model (at the beginning of the analysis) to increase the critical time step size required for stability when the explicit time integration scheme is used. See Remark 2 and warning in Remark 3. (Integer. Default = 0. (Real. the element will be removed in the analysis. Default = 1.0E4) Convergence tolerance EPSII.0.0.0E6) Convergence tolerance EPSIB.0 < Real. Default = 1. the smaller an element size is.0E8) Equilibrium Iteration and Convergence LSEARCH Flag to indicate the use of line searches within the iteration scheme. (Real > 0.0) The minimum time step size used to determine if mass scaling will be applied to elements (at the beginning of the analysis) whose critical time step size is smaller than DTMIN1. Default = 2.
Default = 10) Factor that limits the maximum time step size when the automatic time stepping (ATS) scheme is used. The ATS scheme may increase the time step size after convergence is achieved. (Real) Line search convergence tolerance. the program will stop if convergence is not achieved and the next subdivided time step size is less than DT/ATSSUBD. Default = 0. (Real. Default = 0) 0 – Convergence based on energy 1 – Convergence based on energy and force 2 – Convergence based on energy and displacement 3 – Convergence based on force 4 – Convergence based on displacement Relative energy tolerance.01) Reference force. (Real) Reference rotation. (Integer > 1.01) Reference translation. (Real. (Real) Relative contact force tolerance. (Real. Default = 15) Convergence Criteria. the program will not use a time step size greater than ATSMXDT * DT. (Real) Reference moment. Default = 0. Default = 3.30 Name MAXITE Description Maximum number of iterations within a time step. For a time step size of DT.5) Reference contact force. However. (Real. Default = 0. (Real. for a time step size of DT. (Real. Default = 0. (Real. Default = 0. the program will stop unless the automatic time stepping (ATS) or load displacement control scheme is selected (see parameter AUTO).05) Relative displacement (translation and rotation) tolerance.0) Automatic Time Stepping (ATS) Scheme CONVCRI ETOL RTOL RNORM RMNORM RCTOL DTOL DNORM DMNORM STOL RCONSM ENLSTH ATSSUBD Number that limits the smallest time step size when the automatic time stepping (ATS) scheme is used. (1 < Integer < 999.01) Line search energy threshold. Default = 0.001) Relative force (and moment) tolerance (Real. If the maximum number of iterations is reached without achieving convergence (see CONVCRI parameter).0) ATSMXDT . Default = 0. (Integer.
Default = 1. If current time step size is DT and convergence is not achieved. For contact analysis. i. otherwise ATSNEXT = 1. the original time step size before any subdivision took place is used. 2 – Return to the original time step size. ATSDFAC Division factor used calculate the subincrement time step size. (1< Integer < 6) 1 – X translation 2 – Y translation 3 – Z translation 4 – X rotation 5 – Y rotation 6 – Z rotation Prescribed displacement at grid point LDCGRID for the first solution step.0e4) Load Displacement Control (LDC) Scheme ATSLOWS ATSDAMP LDCGRID LDCDOF Grid point id at which a displacement is prescribed for the first solution step. (Real > 1. (Integer. 3 – Use a time step size such that the solution time matches the original solution time specified by the user. (Real. (Integer > 0) Degree of freedom for prescribed displacement at grid point LDCGRID. (Integer. (Real > 0.0) Flag whether a lowspeed dynamics analysis is performed instead of a static analysis. 1 – Use the time step size that gave convergence.0.CHAPTER 3 Advanced Nonlinear 31 Name ATSNEXT Description Flag controls what time step size to use once convergence is reached after an ATS subdivision. i.e. Default = 0) 0 – Lowspeed dynamics option is not activated 1 – Lowspeed dynamics is performed Damping factor used in lowspeed dynamics analysis. the reduced time step that led to convergence is used again. Default = 0) 0 – Automatically set by program. the next time step size will be DT/ATSDFAC... Default = 2.e. (Real) Displacement convergence factor used to limit the maximum incremental displacement during a solution step. ATSNEXT = 2. Default = 3.0.0) LDCDISP LDCIMAX .
. Default = 0) 0 .Use the old type of contact segment. the smaller will be the subdivided time step size. See Section 6. NSUPP RTSUBD CSTYPE Selects the type of contact segment to use. (Integer.e. (Integer > 1. (0 < Integer < 99. From iteration NSUPP+1.Use the new type of contact segment.4 in Advanced Nonlinear Theory and Modeling Guide for other criteria that determines when an LDC solution will stop. Default = 0) 0 – Solution stops 1 – Solution continues Maximum number of arc length subdivisions allowed. if a target segment in the recorded list is repeated. Default = 10) Contact Control LDCCONT LDCSUBD IMPACT Impact control scheme (Integer. . When the displacement reaches or exceeds LDCDMAX. Default = 0) 0 – Subdivision is based on the magnitude of the tensile contact force. it is “frozen” to be the pairing target segment for the remaining equilibrium iterations in that time step. (Integer. the pairing target segment is recorded for each contactor node. Default = 0) Selects the subdivision scheme used in the implicit rigidtarget contact algorithm when the tensile contact force is too large. Default = 0) 0 – No special treatment is applied for impact problems 1 – Post impact adjustment of velocities and accelerations is applied 2 – Modified parameters are used in Newmark time integration scheme Number of iterations for pairing contactor node to target segment.32 Name LDCDMAX Description Maximum (absolute magnitude) displacement (for the degree of freedom specified by LDCDOF) at the grid point LDCGRID allowed during the analysis. (Integer. Specifying NSUPP > 0 may help in the convergence for certain problems. during the first NSUPP iterations.2. i. (Real) Flag whether the solution is terminated when the first critical point on the equilibrium path is reached. the program will stop the analysis. If NSUPP > 0. 1 – Subdivision is based on the global automatic time stepping (ATS) subdivsion settings. 1 . the larger the magnitude.
the elements are placed into NSUBGRP subgroups for more efficient processing. The filename and location of the restart file is determined by the “dbs” keyword. If a group contains more than 1000 elements and NSUBGRP > 1.0) Frequency of saving the analysis results in the restart file. Default = 0) 0 – Normal analysis run. TSTART* Solution starting time. not a restart analysis 1 – Restart analysis The restart (.res) file from a previous run must exist to do a restart analysis. Normally. Default = 0. TSTART must equal a solution time in which data was saved in a previous run. (Real.e. If TSTART = 0. dbs points to the current working directory with the prefix of the current job name. If MODEX=1. (Integer.CHAPTER 3 Advanced Nonlinear 33 Name MODEX* Description Restart Options Indicates the mode of execution. By default. > 0 – Restart file is overwritten every IRINT time steps < 0 – Restart file is appended every IRINT time steps Other Parameters IRINT* NSUBGRP* Number of subgroups to divide large number of elements with same property ID into. i.0. elements with same type and property ID are placed into a group. (Integer > 0. the last time step in the restart file is used. (Integer. Default = 0) 0 – IRINT is set to 1 when implicit time integration is used and set to the number of steps in the first time step block when explicit time integration is used. Default = 1) Translation Options .
Stiffness of spring elements that simulate RBAR or RBE2 elements. SPRINGK = EMAX * LMODEL where EMAX = maximum Young’s Modulus of materials in the model and LMODEL = largest dimension of the model. (Real.0. Indicates how RBE2 elements are handled. Default = 0) 0 – RBE2 is simulated using rigid option in small displacement analysis and using flexible option in large displacement analysis. simulated by rigid link or constraint equations as determined by program) 2 – RBAR is simulated using flexible option (i. 2 – Convert elements as described above.e. 1 – RBE2 is simulated using rigid option (i. simulated by spring or beam elements as determined by program) 3 – RBAR is simulated by spring elements See Section 2. EQRBAR EQRBE2 SPRINGK . Note that this also converts 6node to 7node triangular (plane strain and axisymmetric) elements and 10node to 11node tetrahedral elements. Indicates how RBAR elements are handled. simulated by spring or beam elements as determined by program) 3 – RBE2 is simulated by spring elements See Section 2.e. 1 – RBAR is simulated using rigid option (i. (Integer. (Integer. nodal coincidence is checked against existing nodes and a new node will not be created at a location if a node already exist at that location. Default = 0) 0 – No conversion of elements 1 – Convert elements as described above.7 of Advanced Nonlinear Theory and Modeling Guide for details on how RBE2 elements are handled.34 Name ELCV Description Convert 8node to 9node quadrilateral (plane strain. simulated by rigid links or constraint equations as determined by program) 2 – RBE2 is simulated using flexible option (i.e. Default = 0) 0 – RBAR is simulated using rigid option in small displacement analysis and using flexible option in large displacement analysis. axisymmetric and shell) elements and 20node to 27node brick elements.e. (Integer. Default = 0. nodal coincidence is not checked against existing nodes and new generated nodes are always created. EMAX is set to 1.7 of Advanced Nonlinear Theory and Modeling Guide for details on how RBAR elements are handled. program automatically sets SPRINGK according to the following calculations.0) If SPRINGK = 0. If no material is specified in the model.0E12.
0 or XDTMIN2 > 0. RBLCRIT = LMODEL * 1. (Real.01)2 where LMODEL = largest dimension of the model Critical length for determining how RBAR and RBE2 elements are simulated when the rigid or flexible option is used to simulate RBAR (see EQRBAR) and RBE2 (see EQRBE2). XDTFAC.0) If BEAME = 0. If XDTMIN1 and XDTMIN2 are both used.0) If BEAMA = 0. 3.0 where EMAX = maximum Young’s Modulus of materials in the model. These parameters are indicated in the table with a superscript ‘o’. XDTMIN1 and DTMIN2 are applied after XMSCALE is applied. IRINT and NSUBGRP parameters can be used for SOL 701. Hence. MODEX. ICMODE. These parameters are indicated in the table with a superscript ‘*’. XDTMIN1 and XDTMIN2 may be used together. extra care should be exercised in examining the results when any of these parameters are used. BEAME is set to EMAX * 100.0E12. • TINT. Default = 0.0E6 • if EQRBAR (or EQRBE2) = 2. program automatically sets BEAMA according to the following calculation: BEAMA = (LMODEL * . Default = 0. XMSCALE. If XDTMIN2 = XDTMIN1 is specified. XDTMIN1 will be ignored.0) If RBLCRIT = 0. Circular cross section area of beam elements that simulate RBAR or RBE2 elements. UPFORM. XDTCAL.0. XMSCALE. TSTART. XDTMIN1 should be greater than XDTMIN2.0. then BEAMA RBLCRIT • if EQRBAR (or EQRBE2) = 1. Default = 0.0. (Real. RBLCRIT = LMODEL * 1. If no material is specified in the model. EMAX is set to 1. DTDELAY. LOADOPT.0 may change the model significantly. Parameters applicable to SOL 701 are: • XSTEP. XDTMIN1 and XDTMIN2 are only used for SOL 701. SDOFANG. 2. . (Real.CHAPTER 3 Advanced Nonlinear 35 Name BEAME Description Young’s Modulus of material assigned to beam elements that simulate RBAR or RBE2 elements.0. XDTMIN1 > 0.0E3 Remarks: 1. WARNING: Specifying XMSCALE > 1.
36 .
MSC.Nastran 2001 Release Guide% CHAPTER 4 Miscellaneous Enhancements ■ SurfacetoSurface Gluing ■ Improvements to AUTOMPC ■ Automatic Resubmitting of NX Nastran Jobs ■ Improvements to AUTOSPC .
Shell elements which use any of the property IDs listed in the BCPROP entry will be included in the . • A glue set can only be defined in the global or first subcase and it will be used in all subcases. For this special case.38 4. Predefined regions of element free faces are used to detect where the glue elements are created. The following should be noted: • Superelements can be used with surfacetosurface gluing as long as the superelements are defined with the SESET bulk entry. These regions can be created using shell elements (BSURF and BCPROP) and using solid element free faces (BSURFS). A region is a collection of element free faces in a section of the model where you expect gluing (or contact) to occur. Defining Glue Regions (BSURF. • In a linear statics solution (SOL 101). a normal is projected. then the solver checks to see if any of these normals intersect with other element free faces. The exception to this is when linear contact is defined in SOL 101. • and the distance between the two faces is equal to or less than the defined separation distance. The glue option creates stiff springs to connect the predefined surfaces and prevents relative motion in all directions. Glue definitions can be used in all solution sequences except for SOL 601 and 701. glue sets can be defined in any subcase. The BSURF entry is defined by its own unique ID and is a list or range of shell element IDs to include in the region. The BCPROP entry is defined by its own unique ID and is a list of shell element property IDs. the springs created by the solver from glue definitions will be referred to as “glue elements” in the documentation. From each element free face. surface gluing and surface contact can be defined for the same subcase. This limitation will be removed in NXN5. BCPROP and BSURFS Bulk Entries) You must first define the regions where you would like the solver to create glue elements. A glue element is created during the solution if: • NX Nastran finds an intersection between element faces. For discussion purposes.1 SurfacetoSurface Gluing Introduction A new option to “glue” element faces together during a solution is available in this release of NX Nastran.
Defining Glue Pairs (New BGSET Case Control and Bulk Entry) Two new commands have been created in this release to define glue conditions for the solution. (See chapter 15 of the NX Nastran User’s Guide for information on using consistent normals) When shell elements are used as the source in a contact pair. On the BCRPARA bulk entry. The BSURFS entry is defined by its own unique ID and is a list of solid element IDs each followed by 3 grid points defining which face of the 3D element to include in the glue region. source and target. and the normal will be projected from the bottom side. The top side of a shell element is determined by the order and direction of grid points on the element’s definition and the righthand rule. BCPROP and BSURFS entries. the solve will use the top side to project the element normal while searching for the target elements. When a source region is made from shell elements (BSURF or BCPROP). Understanding shell element normals. The BSURF. If the . CRID and SURF are the only fields used by glue regions. the new BGSET case control command. and making sure they are consistent in the source regions is very important to ensuring that glue elements will be created as expected. The default value of SDIST of 100 is large enough to handle most geometry situations. you can set the SURF option to “BOT”. in which gluing will be analyzed during the solution. In the case where the target is on the bottom side. A glue pair is a way to combine two regions. The SIDi and TIDi fields refer to regions created by the BSURF. and the new BGSET bulk entry. and are used to define source and target regions respectively for a pair. but can be adjusted as needed. An element should not appear more than once in the regions that are part of a glue/contact pair. at the beginning of the solution. The GSID field will need to match the value of ‘n’ on the new BGSET case control entry for the solution to recognize this glue definition. BCPROP and BSURFS entries described are used to define glue and/or contact regions. Recall that NX Nastran projects normals from element faces and then checks to see if any of these normals intersect with another element free face. As many pairs as desired can be included on a single BGSET entry. to determine where glue elements need to be initially created. the SURF field on the BCRPARA bulk entry may be needed to alter the search direction.CHAPTER 4 Miscellaneous Enhancements 39 region. The search distance field (SDIST) defines the distance in which the solver can initially determine if the distance between element faces in a particular pair are within the threshold for creating glue elements. This value is used once. The new BGSET bulk entry is used to define each glue pair. by default. both of which are included below.
but can be adjusted if separation of the surfaces is observed. (Integer>0) Glue Contact Set Selection Selects the glue contact set. These files will all start with “glue” following with a solution number. Examples have been provided in the install location NX_Nastran_Install_Path/nxn4/nast/tpl to demonstrate capabilities and to show the correct syntax for surfacetosurface gluing. New BGSET Bulk Data Entry BGSET Format: 3D Glue Contact Set Definition Defines glued contact pairs of a 3D set. one of the files is glue103. 1 BGSET 2 GSID 3 SID1 SID2 etc 4 TID1 TID2 5 SDIST1 SDIST2 6 PEN 7 8 9 10 .dat. The default penalty factor is sufficient for most cases. a glue element is created. New BGSET Case Control Card BGSET Format: BGSET=n Examples: BGSET=5 Describers n Meaning Glue contact set identification of a BGSET Bulk Data entry. and the distance between the two element faces is within the range defined on the SDIST fields. which is used to adjust the stiffness of the glue condition. The remaining field on the BGSET bulk entry is the penalty (PEN) factor.40 projected normal intersects an element face. For example.
(Integer > 0) Search distance for glue surfaces (Real). The default search distance will glue all overlapping sections of the source and target regions. (Real). Increase it if separation of the surfaces is observed. (Integer>0) Source region identification number of glue pair i. numerical problems may occur. The default penalty factor will be sufficient for most cases. .(Default= 100) Penalty value used in calculations.(Default = 1.0E5) 1. 2.CHAPTER 4 Miscellaneous Enhancements 41 Example: BGSET 4 1 4 2 3 Field GSID SIDi TIDi SDISTi PEN Remarks: Contents Glue set identification number. The value defined on the first line will be used for all pairs. If defined too large. This value can be used in special cases to control what subregions are to be glued. (Integer > 0) Target region identification number for glue pair i.
An updated version of the AUTOMPC parameter is included below. • When the AUTOMPC was originally created in version 3. the Parameter AUTOMPC was introduced as an automatic way of processing the dependent and independent degreeoffreedom for rigid elements.2 Improvements to AUTOMPC In version 3 of NX Nastran. particularily with large numbers of RBE3 elements containing large numbers of grids. In version 4. the following improvements have been made to AUTOMPC: • Models with large numbers of MPC equations. will see performance improvements.1.1. Before AUTOMPC was created. This is done by including a list of degreeoffreedom on USET/USET1 bulk data cards and making them part of the U5 set. . Including dof as part of the U4 set specifies they must be made part of the mset. This was a tedious process for models with large numbers of contraints. an option to do the opposite has been created. you were required to select independent and dependent degreeoffreedom when creating rigid elements.42 4. constraint elements and MPC equations. Now in version 4. an option was created to specify that a dof (a dof which is included in an MPC equation) must not be made part of the mset. constraint elements and MPC equations.
etc. If an RBE3 element contains UM information on the mset data. In addition. SPOINTS in MPC equations will always be made part of the mset. those dofs will be used in the mset. using USET/USET1 bulk data cards. any redundant constraints will be eliminated.) in the bulk data definition except as noted below. This option relieves the need to carefully define rigid elements (or MPCs) so as to not have a conflict of the msets between elements. If specified. This option is not available in some circumstances and will be automatically set to NO for: 1) A pelement analysis with local coordinate systems or RSSCON elements. but making them part of the U4 set. This is accomplished by defining these dofs on USET/USET1 bulk data cards making them part of the U5 set. RBAR. . it is possible to specify that selected dof must not be made part of the mset. 2) A design optimization solution (SOL=200) with DVGRID data. RROD.CHAPTER 4 Miscellaneous Enhancements 43 Updated Version of the AUTOMPC Parameter AUTOMPC Default=NO AUTOMPC=YES specifies that the software automatically selects the mset dofs rather than use the mset values as specified on MPC or RIGID element cards (RBE*. Again. The AUTOMPC option is recommended for use in models with RSSCON elements connected to CPENTA elements. the UM information on RBE3 elements will be ignored. When using this option. An option also exists to specify that selected dof must be made part of the mset.
an option to have the job retried automatically is now available. .3 Automatic Resubmitting of NX Nastran Jobs When an NX Nastran job fails because of a failed license request. The default is 20 minutes.44 4. NX Nastran will now retry a failed license request job every minute up to the value of the AUTHQUEUE keyword.
CHAPTER 4 Miscellaneous Enhancements 45 4. System Cell Number System Cell Name SVDSPC Function and Reference Determines which AUTOSPC method is used. The SVD method is numerically more reliable and should be turned on in cases when you find unexpected singularities remaining after the AUTOSPC operation. but SVD can be selected using the new system cell SVDSPC=1.4 Improvements to AUTOSPC The Singular Value Decomposition (SVD) method is now available to AUTOSPC unrestrained conditions in your model. 0: Use the eigenvalue method (Default) 1: Use the Singular Value Decomposition (SVD) method 419 . The eigenvalue method is still used by default.
46 .
0 to 4.Nastran 2001 Release Guide APPENDIX A Upward Compatibility ■ DMAP Module Additions/Changes from NX Nastran 4.1 .0 to 4.MSC.1 ■ Datablock Additions/Changes from NX Nastran 4.
0 to 4.1 The following DMAP modules are additions or have changed in this release: • GP4 • OFP .48 A.1 DMAP Module Additions/Changes from NX Nastran 4.
YS0.MPCF2/S. Grid point definition table. and the enforced motion partitioning vector.CSTM.. Table of coordinate system transformation matrices.N.SIL.N. multipoint constraints.USET0.GEOM2. the multipoint constraint equation matrix.CHAPTER A Upward Compatibility 49 GP4 Generates the degreeoffreedom set table Generates the degreeoffreedom set table based on single point constraints.NOOSET/ S.N.BGPDT. MEDGE. Table of Bulk Data entry images related to constraints. Table of grid points generated for pelement analysis. .g.PARTV/ LUSET/S.N. Format: GP4 CASECC.N. Basic grid point definition table.N.N. Face table for pelement analysis.NOMSET/S. Equivalence table between external and internal grid/scalar identification numbers. ASET).MFACE. Body table for pelement analysis.NORSET/S. Also generates the enforced displacement matrix. Edge table for pelement analysis.REPEAT/S. Scalar index list.N.NSKIP/S.N.NOL/ S. and set membership assignment Bulk Data entries (e.MBODY.GEOM4.NOSET/S. Table of Bulk Data entry images related to element connectivity and scalar points. rigid elements. degreeoffreedom membership and rigid element connectivity.GDNTAB/ RMG.NOSSET/S.N.GPDT.NOA/SEID/ALTSHAPE/SEBULK/DMAPNO/AUTOMPC $ Input Data Blocks: CASECC GEOM4 EQEXIN SIL GPDT BGPDT CSTM MEDGE MFACE MBODY GEOM2 GDNTAB Table of Case Control command images.EQEXIN.
50
Output Data Blocks: RMG YS0 USET0 PARTV Parameters: LUSET NOMSET Inputintegerdefault=0. The number of degreesoffreedom in the gset. Outputintegerno default. Number of degreesoffreedom in the mset or multipoint constraint and rigid element flag. Set to 1 if there are none. Outputintegerno default. Multipoint constraint set identification number change flag. Set to 1 if the current subcase contains a different multipoint constraint set from the previous subcase. Set to 1 otherwise or if there are no multipoint constraints in the current subcase. Outputintegerno default. Number of degreesoffreedom in the sset. or single point constraint flag. Set to 1 if there are none. Outputintegerno default. Number of degreesoffreedom in the oset or omitted degreeoffreedom flag. Set to 1 if there are none. Outputintegerno default. Number of degreesoffreedom in the rset. or supported degreeoffreedom flag. Set to 1 if there are none. Input/outputintegerno default. The record number in CASECC corresponding to the first subcase of the current boundary condition. Outputintegerno default. Last boundary condition flag. Set to 1 at the last boundary condition; +1 otherwise. Outputintegerno default. Constraint, omit, and support set flag. Set to 1 if NOMSET=1, NOSSET=1, NOOSET=1, NORSET=1 and no degreesoffreedom defined in the aset (e.g., ASETi, QSETi Bulk Data entries); +1 otherwise. Outputintegerdefault=1. Dependent set flag. Set to 1 if all degreesoffreedom belong to mset, sset, oset, and/or rset; otherwise, the degreesoffreedom in the lset. Outputintegerdefault=1. Constraint and omit set flag. Set to 1 if NOMSET=1, NOSSET=1, and NOOSET=1; otherwise the number of degreesoffreedom in the aset. Inputintegerdefault=0. Superelement identification number. Multipoint constraint equation matrix. Matrix of enforced displacements. Degreeoffreedom set membership table for gset. Partitioning vector of enforced motion dof.
MPCF2
NOSSET NOOSET NORSET NSKIP REPEAT NOSET
NOL
NOA
SEID
CHAPTER A
Upward Compatibility
51
ALTSHAPE Inputintegerdefault=0. Specifies set of displacement functions in pelement analysis. ALTSHAPE=0 selects the MacNeal set and 1 selects the Full Product Space set. SEBULK Inputlogicaldefault=FALSE. Partitioned superelement presence flag. Set to TRUE if partitioned superelements are present or BEGIN SUPER is specified for the first BEGIN BULK Case Control command. Inputintegerdefault=0. DMAP solution number.
DMAPNO
AUTOMPC Inputcharacterdefault=NO. Auto MPC processing flag. Remarks: 1. YS and PARTV will be purged if SPCD or SPC Bulk Data entries do not specify nonzero values for displacement, velocity, or acceleration. 2. GEOM4 may be purged. 3. CSTM may be purged if no coordinate systems are used.
52
OFP
Output file processor
To output (print or punch) data blocks prepared by other modules in useroriented, selfexplanatory formats. Format: OFP OFP1,OFP2,OFP3,OFP4,OFP5,OFP6, CSTM,BGPDTVU,ERROR1,DEQATN,DEQIND,DIT// S,N,CARDNO/ODCODE/PVALID/DFLAG/VFLAG/AFLAG $
Input Data Blocks: OFPi CSTM EHT BGPDTVU ERROR1 DEQATN DEQIND DIT Output table suitable for processing by the OFP module. See Remark 2. Table of coordinate system transformation matrices. Element hierarchical table for pelement analysis. Basic grid point definition table for a superelement and related to geometry with viewgrids added. Errorestimate table updated for current superelement or adaptivity loop. Table of DEQATN Bulk Data entry images. Index table to DEQATN data block. Table of TABLEDi Bulk Data entry images.
Output Data Blocks: None. Parameters: CARDNO Input/outputintegerdefault=0. Punch file line counter. CARDNO is incremented by one for each line written to the punch file and is also written into columns 7380 of each line. Inputintegerdefault=1. Output device code override. See Remark 4. ODCODE overrides the code stored in the DBi's according to the following table: ODCODE 1 2 3 Output Directed to: Print Plot Print and Plot
ODCODE
VDR. stress. Acceleration output flag. DMAP modules READ (LAMA. i. BGPDTVU. SDRX. and GPWG. Inputintegerdefault=0. LAMX. Parameter ODCODE is not honored by data blocks LAMA.. LAMX. EHT. DDRMM. 2. OEIGS. . SDR3. and LAMX (LAMB) are matrix operation modules that prepare OFP formatted data blocks. CEAD (CLAMA and OCEIGS). CLAMX). VDRE. OEIGS. etc. DRMH3. = 0 output velocity “as is” = 1 output velocity as “relative motion” = 2 do not output velocity AFLAG Inputintegerdefault=0. CLAMA. CSTM. GPFDR. strain. Modules SDR2. Pelement adaptivity loop identification number. = 0 output acceleration “as is” = 1 output acceleration as “relative motion” = 2 do not output acceleration Remarks: 1. CURV. Velocity output flag. ELFDR. and ERROR1 are required if pelements are specified and only for data recovery. Displacement output flag. 4. LAMX. and OGPWG. SDRCOMP. ADR. GPWG. Any or all data blocks may be purged. LAMX. and SDRHT also prepare OFP formatted data blocks. displacement. 3. = 0 output displacement “as is” = 1 output displacement as “relative motion” = 2 do not output displacement VFLAG Inputintegerdefault=0. which are created by READ.e. and Punch Inputintegerdefault=0. Plot.CHAPTER A Upward Compatibility 53 4 5 6 7 PVALID DFLAG Punch Print and Punch Plot and Punch Print. CEAD. MDATA.
strain. i. DEQATN. CSTM.. DEQIND.e. displacement. stress. and DIT are required if the CORD3G Bulk Data entry is present and only for element data recovery. etc. Example: Print the OUG1 table from the SDR2 module: OFP OUG1/ $ .54 5.
2 Datablock Additions/Changes from NX Nastran 4.0 to 4.CHAPTER A Upward Compatibility 55 A.1 The following Datablocks are additions or have changed in this release: • OCPSDF .
3=complex) Length of entries in RECORD=DATA (always 3) Type of first response quantity Element. Record 0 .56 OCPSDF Table of crosspower spectral density functions.HEADER Word 1 Name NAME(2) Type CHAR4 Block Name Description Record 1 .IDENT Word 1 2 3 4 5 6 7 9 10 11 12 13 14 15 16 17 18 51 Name ACODE(C) TCODE(C) UNDEF RANDID CCODE RCROID UNDEF(2) OCODE NUMWDE(C) RTYPE1 ID1 COMP1 RTYPE2 ID2 COMP2 CURID UNDEF(33) TITLE(32) Type I I none I I I none I I CHAR4 I I CHAR4 I I I none CHAR4 Title Output code (2=real. grid. grid or scalar point ID number Component code (item) ID number Type of second response quantity Element. always 4100 . Table of crosspower spectral density functions. or scalar point ID number Component code (item) ID number Curve ID number RANDOM set identification number Device code +10*function number RCROSS identification number Description Device code + 10*Approach code Table code.
. Approach code: 1 = statics 2 = reigen 3 = ds0 4 = ds1 5 = freq Name WORD1 WORD2 UNDEF(5) Type I I none Description Number of records Number of data values in record 2. Words 13 in record 2 repeat for each frequency. Records repeat for each subcase having any output requests.TRAILER Word 1 2 3 Notes: 1. 2.CHAPTER A Upward Compatibility 57 Word 83 115 Name SUBTITL(32) LABEL(32) Type CHAR4 CHAR4 Subtitle Label Description Record 2 . Records 1 and 2 repeat for each function generated.DATA Word 1 2 3 Name FREQ RPSDF IPSDF Type RS RS RS Description Frequency (Hz) Real part of crosspower spectral density function value Imaginary part of crosspower spectral density function value Record 3 . Device code: 1 = print 4 = punch 5 = print and punch 3.
RTYPEi: DISP = displacement VELO = velocity ACCE = acceleration OLOA = applied loads SPCF = singlepoint constraint force MPCF = multipoint constraint force STRE = stress STRA = strain FORC = force .58 6 = bkl0 7 = bkl1 8 = ceigen 9 = pla 4.
Nastran 2001 Release Guide APPENDIX B System Descriptions ■ Supported System Configurations for NX Nastran 4.MSC.1 .
3700. 4000.8Ghz Description Description Red Hat 7. 715. 6750 PARISC: HPUX B. 778. Red Hat EL 3. 4900.1 Supported System Configurations for NX Nastran 4.2. 800. 819. 712.60 B.11.1 System Description – HP9000 – HPUX Item Supported Model(s) Configurations for Installed Timing Constants Build Operating System Other Supported Operating Systems Word Length Build Type PARISC 250. ILP32 DMP . Red Hat EL 4. 2733.3 Suse 9. 735.00 HPUX B.11 32 bits LP64. 730. 2600.11.0 32 bits ILP32. 889. 710. LP64 DMP System Description – Intel – Linux Item Supported Model(s) Configurations for Installed Timing Constants Build Operating System Other Supported Operating Systems Word Length Build Type Intel and Intelcompatible P4 2.0. 2200. 720.
397. ILP64: 64 bits LP64. IP21. IP19. 950. Power3.1 AIX 5. Description Windows 2000.5GHz. R10K. LP64 DMP. 980.5. 580. WXP SP2.2. 570. R12K – IRIX64 Item Supported Model(s) Configurations for Installed Timing Constants Build Operating System R8K. R10K. Pentium Pro. SP3 WXP SP1. 590. Win 2003 Server (on EM64T/Opteron) 32 bits ILP32 System Description – IBM RS/6000 – AIX (64 bit) Item Supported Model(s) Installed Timing Constants Build Operating System Other Supported Operating Systems Word Length Build Type Description Power. 990. IP28. 530h. Power4 303.CHAPTER B System Descriptions 61 System Description – Intel – Windows (32bit) Item Supported Model(s) Configurations for Installed Timing Constants Build Operating System Other Supported Operating Systems Word Length Build Type Intel and Intelcompatible Pentium II 400 MHz. IP27. 560. 390. R16K IP7. 591. IP30. 4316 AIX 5. 510 Description IRIX 6.320H. AIX 5. 370. ILP64. Power2. WXP64 (on EM64T/Opteron). 530. IP22. IP20.7 . ILP64 DMP System Description – SGI R8K. 550. 240. 375. IP35. R12K. P4 1.3 LP64: 32 bits.
Red Hat EL 4.0. ILP64 DMP Description .21. IRIX 6.27m 32 bits LP64. R12K – IRIX64 Item Other Supported Operating Systems Word Length Build Type Description IRIX 6. Suse 9.5.5. LP64 DMP System Description – Sun SPARC – Solaris Item Supported Model(s) Installed Timing Constants Build Operating System Other Supported Operating Systems Word Length Build Type UltraSPARC UltraSPARC (75 & 95) UltraSPARC:Solaris 8 Solaris 9.24m. IRIX 6. LP64 DMP. ILP64.5.0 Suse 9.62 System Description – SGI R8K. R10K. Solaris 10 32 bits LP64 Description System Description – X86_64 Linux (AMD Opteron/EM64T) Item Supported Model(s) Installed Timing Constants Build Operating System Other Supported Operating Systems Word Length Build Type X8664 Linux 8664 SuSE 9. ILP64: 64 bits LP64. Suse SLES9.0 LP64: 32 bits. Red Hat EL 3.1.3.
ILP64: 64 bits LP64.CHAPTER B System Descriptions 63 System Description – Intel Itanium HPUX Item Supported Model(s) Installed Timing Constants Build Operating System Other Supported Operating Systems Word Length Build Type IntelItaniumHPUX 4900. ILP64 DMP System Description – SGI Altix Item Supported Model(s) Installed Timing Constants Build Operating System Other Supported Operating Systems SGIALTIX 6402 SGI ProPack 3 sp3 SGI ProPack 4 Description Description Description .22 HPUX B.0. 5400 HPUX B. ILP64. ILP64. 5300. ILP64: 64 bits LP64.23 LP64: 32 bits. LP64 DMP.11. Red Hat EL4.0 LP64: 32 bits. ILP64 DMP System Description – Intel Itanium Linux Item Supported Model(s) Installed Timing Constants Build Operating System Other Supported Operating Systems Word Length Build Type Itanium II IA64 800 Mhz & 733Mhz Red Hat AW2.11.1 Red Hat EL3. LP64 DMP.
733 MHz Itanium 32 Bit. LP64 DMP. ILP64: 64 bits LP64. ILP64 DMP System Description – Intel (EM64T/Opteron) – Windows (64 bit) Item Supported Model(s) Configurations for Installed Timing Constants Build Operating System Other Supported Operating Systems Word Length Build Type Intel and Intelcompatible Pentium II 400 MHz. P4 1.64 System Description – SGI Altix Item Word Length Build Type Description LP64: 32 bits. Windows 2003 Server WXP64 32 bits LP64 Description . Pentium Pro. ILP64.5GHz.
This action might not be possible to undo. Are you sure you want to continue?
Use one of your book credits to continue reading from where you left off, or restart the preview.