In the coded database file Jobname.CDB, most ANSYS commands have the same format they have elsewhere. (See the Command Reference for command-specific information.) However, the format for some commands differs slightly in the Jobname.CDB file. The format for these commands is described below.
The CDWRITE command has an UNBLOCKED and a BLOCKED option. The UNBLOCKED option writes all data out in command format. The default BLOCKED option writes certain data items in a fixed format, including those that could potentially contain large amounts of data, such as nodal data.
The CE command defines the constant term in a constraint equation. The command format in Jobname.CDB is:
CE,R5.0,Type,LENGTH,NCE,CONSTType
The type of data to be defined. DEFI is the valid label.
LENGTH
The total number of variable terms in the constraint equation.
NCE
The constraint equation reference number.
CONST
The constant term of the equation.
Another version of the CE command defines the variable terms in a constraint equation. You must issue this version of the command after the CE command described above. This command repeats until all terms are defined.
The alternate format for the CE command is:
CE,R5.0,Type,N1,Dlab1,C1,N2,Dlab2,C2Type
The type of data to be defined. NODE is the valid label.
N1
The node number of the next term.
Dlab1
The DOF label of N1.
C1
The coefficient of N1.
N2
The node number of the next term.
Dlab2
The DOF label of N2.
C2
The coefficient of N2.
The CP command defines a coupled node set. You repeat the command until all nodes are defined. The command format in Jobname.CDB is:
CP,R5.0,LENGTH,NCP,Dlab,N1,N2,N3,N4,N5,N6,N7LENGTH
The total number of nodes in the coupled set
NCP
The coupled node reference number
Dlab
The degree of freedom label for the set
N1,N2,N3,N4,N5,N6,N7The next seven node numbers in the coupled set
The CMBLOCK command defines the entities contained in a node or element component. The command format in Jobname.CDB is:
CMBLOCK,Cname,Entity,NUMITEMS
FormatCname
Eight character component name.
Entity
Label identifying the type of component (NODE or ELEMENT).
NUMITEMS
Number of items written.
Data descriptors defining the format. For CMBLOCK this is always (8i10).
The items contained in this component are written at 10 items per line. Additional
lines are repeated as needed until all NumItems are
defined. If one of the items is less than zero, then the entities from the item
previous to this one (inclusive) are part of the component.
The CMBLOCK command is not valid in a *DO loop.
The CYCLIC,CDWR command defines the input and output of a cyclic symmetry analysis. The syntax is:
CYCLIC,CDWR,Value1,Value2,Value3,...
The following describes the values written to the .CDB file for cyclic options CYCLIC,CDWR:
Value1 = 1Value2
Number of cyclic sectors
Value3
Number of solutions in cyclic space
Value4
Harmonic index of this load
Value5
Cyclic coordinate system
Value6
| < 0 or Static: only solve for given harmonic indices from CYCOPT,HIND |
| > 0: tolerance for the Fourier load |
Value1 = 2Value2
Cyclic edge type (0 = undefined; 1 = areas; 10 = lines; 100 = keypoints; 1000 = nodes)
Value3
0 or blank
Value4
Maximum possible harmonic index
Value5
Force load coordinate system (1 = global coordinate system; 0 = cyclic coordinate system)
Value6
Inertia load coordinate system (1 = global coordinate system; 0 = cyclic coordinate system)
Value1 = 3 - 22Value2 -
Value6Cyclic edge constraint equation/coupling degree of freedom (DOF) (0 = all available DOF; otherwise bitmap) for pair IDs 1-5
(Repeat as necessary for other pair IDs
(Value1 = 4 - 22))
Value1 = 23 - 30Cyclic harmonic index bit bins (each bin holds 32 harmonic indices by
5 containers corresponding to Value2 -
Value6)
Value2 -
Value6Cyclic harmonic index bits (0 = solve for harmonic index; nonzero values indicate skipped harmonic indices)
Value1 = 31Value2
Max node number in base sector
Value3
Max element number in base sector
Value4
Number of defined nodes in base sector
Value5
Number of defined elements in base sector
Value1 = 32Value2
/CYCEXPAND number of sectors to expand (total)
Value3
Number of edge component pairs
Value4 -
Value8/CYCEXPAND number of sectors to expand (per window)
Value1 = 33Not used
Value1 = 34Cyclic CSYS coordinate system integer data (part 1)
Value2
Theta singularity key
Value3
Phi singularity key
Value4
Coordinate system type
Value1 = 35Cyclic CSYS coordinate system integer data (part 2)
Value2
Coordinate system number
Value3
Not used (defaults to 0)
Value4
Not used (defaults to 0)
Value1 = 36Value2
Number of user-defined cyclic edge pair components
Value3
Rotate cyclic edge nodes into cyclic coordinate system (0 = rotate edge nodes (default); 1 = do not rotate edge nodes)
Value4
NLGEOM flag (0 = no NLGEOM effects (default); 1 = include NLGEOM effects)
Value5
Sector edge display key (-1 = suppresses display of edges between sectors even if the cyclic count varies between active windows; 0 = averages stresses or strains across sector boundaries. This value is the default (although the default reverts to 1 or ON if the cyclic count varies between active windows); 1 = no averaging of stresses or strains occurs and sector boundaries are shown on the plot)
Value1 = 101Value2
Sector angle (degrees)
Value3
XYZ tolerance input for matching low/high nodes
Value4
Angle tolerance for matching low/high nodes (degrees)
Value5
Tolerance in the element coordinate system for unequal meshes
Value1 = 102 - 104Cyclic CSYS coordinate system double precision data (part 1)
Value2 -
Value4Coordinate system transformation matrix (total of 9 values)
Value1 = 105Cyclic CSYS coordinate system double precision data (part 2)
Value2 -
Value4Origin location (XYZ)
Value1 = 106Cyclic CSYS coordinate system double precision data (part 3)
Value2
Used for elliptical, spheroidal, or toroidal systems. If
CSYS = 1 or 2, Value2 is the
ratio of the ellipse Y-axis radius to X-axis radius
(defaults to 1.0 (circle))
Value3
Used for spheroidal systems. If CSYS = 2,
Value3 is the ratio of
ellipse Z-axis radius to X-axis radius (defaults to 1.0
(circle))
Value1 = 107Cyclic CSYS coordinate system double precision data (part 4)
Value2
First rotation about local Z (positive X toward Y)
Value3
Second rotation about local X (positive Y toward Z)
Value4
Third rotation about local X (positive Z toward X)
Value1 = 121Value2
Root of component names defining low and high ranges
Value1 = 122Value2
Cyclic low/high xref array parameter name (node)
Value1 = 123Value2
Cyclic low/high xref array parameter name (line)
Value1 = 124Value2
Cyclic low/high xref array parameter name (area)
Value1 = 125Value2
The component name of the elements to expand (see /CYCEXPAND,,WHAT)
Value1 = 201Value2
Total number of modes extracted during a cyclic modal solve. This value is only available after call to CYCCALC.
Value3
Mode superposition flag to limit results written to .MODE and .RST files
Value4
Excitation engine order
Value1 = 202Value2
Type of mistuning (1 = stiffness; 2 = mass; 3 = both; -1 = use user macro CYCMSUPUSERSOLVE)
Value3
Cyclic mode superposition restart flag (1 = new frequency sweep; 2 = new mistuning parameters; -1 = form blade superelement and stop)
Value4
Cyclic mode superposition key to perform complex modal analysis of reduced system
Value5
Number of CMS modes for mistuned reduced order model (see CYCFREQ,BLADE)
Value1 = 203Value2
Array name for aerodynamic coupling coefficients
Value1 = 204Unused
Value1 = 205Value2
The name of the nodal component containing the blade boundary nodes at the blade-to-disk interface (see CYCFREQ,BLADE). This is used for cyclic mode superposition analyses that include mistuning or aero coupling.
Value1 = 206Value2
The name of the element component containing the blade superelements (see CYCFREQ,BLADE). This is used for cyclic mode superposition analyses that include mistuning or aero coupling.
Value1 = 207Value2
The name of the array holding stiffness mistuning parameters
Value1 = 208Unused
Value1 = 209Rotational velocity from the base linear perturbation analysis.
Value2
X-component of rotational velocity
Value3
Y-component of rotational velocity
Value4
Z-component of rotational velocity
Value1 = 210Value2
Beginning of frequency range for CMS modes (see CYCFREQ,BLADE). This is used for cyclic mode superposition analyses that include mistuning or aero coupling.
Value3
End of frequency range for CMS modes (see CYCFREQ,BLADE). This is used for cyclic mode superposition analyses that include mistuning or aero coupling.
Value1 = 211Value2
Number of modes for a cyclic mode superposition damped modal solve
Value3
Beginning of frequency range for cyclic mode superposition damped modal solve
Value4
End of frequency range for cyclic mode superposition damped modal solve
The EBLOCK command defines a block of elements. The command syntax is:
EBLOCK, NUM_NODES, Solkey Format
NUM_NODES
The number of nodes to be read in the first line of an element definition.
Solkey
The solid model key. The element is part of a solid model if the
keyword SOLID appears here. When Solkey =
SOLID, Field 8 (the element shape flag) may be left at zero, and Field 9
is the number of nodes defining this element.
Data descriptors defining the format.
The format of the element "block" is as follows for the SOLID format:
Field 1 - The material number.
Field 2 - The element type number.
Field 3 - The real constant number.
Field 4 - The section ID attribute (beam section) number.
Field 5 - The element coordinate system number.
Field 6 - The birth/death flag.
Field 7 - The solid model reference number.
Field 8 - The element shape flag.
Field 9 - The number of nodes defining this element if
Solkey = SOLID; otherwise, Field 9 =
0.
Field 10 - Not used.
Field 11 - The element number.
Fields 12-19 - The node numbers. The next line will have the additional node numbers if there are more than eight.
The format without the SOLID keyword is:
Field 1 - The element number.
Field 2 - The type of section ID.
Field 3 - The real constant number.
Field 4 - The material number.
Field 5 - The element coordinate system number.
Fields 6-15 - The node numbers. The next line will have the additional node numbers if there are more than ten.
The final line of the block will be a -1 in field 1.
If you are in the GUI, the EBLOCK command must be contained in an externally prepared file and read into ANSYS (i.e., CDREAD, /INPUT, etc.).
The EBLOCK command is not valid in a *DO loop.
The EDCADAPT command specifies adaptive meshing control for explicit dynamics analysis. The command format in Jobname.CDB is:
EDCADAPT,R5.3,FREQ,TOL,OPT,MAXLVL,BTIME,DTIME,LCID,ADPSIZE,ADPASS,IREFLG,ADPENE,ADPTH,MAXELFREQ
The time interval between adaptive mesh refinement.
TOL
The adaptive angle tolerance (in degrees).
OPT
The adaptivity option.
MAXLVL
The maximum number of mesh refinement levels.
BTIME
The birth time to begin adaptive meshing.
DTIME
The death time to end adaptive meshing.
LCID
The curve ID defined by EDCURVE
ADPSIZE
The minimum element size to be adapted, based on the element edge length.
ADPASS
The one-pass or two-pass adaptivity option.
IREFLG
The uniform refinement level flag.
ADPENE
Adaptive mesh flag for starting adaptivity when approaching (positive
ADPENE) or penetrating (negative
ADPENE) the tooling surface
ADPTH
Absolute shell thickness level below which adaptivity should begin.
MAXEL
The maximum number of elements at which adaptivity will be terminated.
This command also appears in the Command Reference. The format shown here contains information specific to the CDREAD/CDWRITE file.
The EDCGEN command is used to define a contact definition for explicit dynamics. The command format in Jobname.CDB is:
EDCGEN,R5.3,Option,Cont,Targ,Lkey,FS,FD,DC,VC,VDC,V1,V2,V3,V4,BTIME,DTIME,BOXID1,BOXID2Option
The label identifying the contact behavior.
Cont
The contact surface, identified by component name, part ID, or part assembly ID.
Targ
The target surface, identified by component name, part ID, or part assembly ID.
Lkey
A key identifying the meaning of Cont and
Targ (component, part or part assembly).
FS
The static friction coefficient.
FD
The dynamic friction coefficient.
DC
The exponential decay coefficient.
VC
The coefficient of viscous friction.
VDC
The viscous damping coefficient in percent of critical damping.
V1,V2,V3,V4
Additional input for some contact types. See EDCGEN in the Command Reference for more information.
BTIME
The birth time for which conatct definition will become active.
DTIME
The death time for which conatct definition will become inactive.
BOXID1
Contact volume as defined using EDBOX
BOXID2
Target volume as defined using EDBOX
This command also appears in the Command Reference. The format shown here contains information specific to the CDREAD/CDWRITE file.
The EDCURVE command is used to define a curve for an explicit dynamics analysis. The command format in Jobname.CDB is:
EDCURVE,R5.3,Option,LCID,Length,0.0,Par1,Par2Option
The EDCURVE command option. The only valid option is “ADD.”
LCID
The curve ID.
Length
The number of data values for the abcissa array
(Par1) and the ordinate array
(Par2).
Par1
The abcissa values, repeat Length number of
times.
Par2
The ordinate values, repeat Length number
of times.
This command also appears in the Command Reference. The format shown here contains information specific to the CDREAD/CDWRITE file.
The EDDRELAX command activates initialization to a prescribed geometry or dynamic relaxation for the explicit analysis. The command format in Jobname.CDB is:
EDDRELAX,R5.4,Option,NRCYCK,IRELAL,EDTTL,DRTOL,DFFCTR,DRTERM,TSSFDROption
EDDRELAX command option. Valid options are
“ANSYS” (relaxation is based on the implicit analysis, see
the EDDRELAX command in the Command Reference) or
“DYNA,” where the relaxation parameters are controlled
within the LS-DYNA analysis. The following arguments are valid for
Option= DYNA only.
NRCYCK
The number of iterations between the convergence checks.
IRELAL
Automatic control based on Papadrakakis not active (0) or active (1).
EDTTL
The convergence tolerance when automatic control is used.
DRTOL
The convergence tolerance.
DFFCTR
The dynamic relaxation factor.
DRTERM
The termination time for dynamic relaxation.
TSSFDR
The scale factor for each computed time step.
This command also appears in the Command Reference. The format shown here contains information specific to the CDREAD/CDWRITE file.
The EDLCS command is used to define a local coordinate system for explicit dynamics. The command format in Jobname.CDB is:
EDLCS,R5.3,Option,CID,X1,Y1,Z1,X2,Y2,Z2,X3,Y3,Z3Option
The EDLCS command option. The only valid option is “ADD.”
CID
The coordinate system ID.
X1,Y1,Z1,The X,Y,Z coordinate of a point on the local X-axis.
X2,Y2,Z2,The X,Y,Z coordinate of a point on the local X-Y plane.
X3,Y3,Z3,The X,Y,Z coordinate of the local origin.
This command also appears in the Command Reference. The format shown here contains information specific to the CDREAD/CDWRITE file.
The EDLOAD command is used to define loading conditions for explicit dynamics. The command format in Jobname.CDB is:
EDLOAD,R5.3,Option,Lab,KEY,Cname,Length,PHASE,Par1,Par2,LCID,SCALE,BTIME,DTIMEOption
The EDLOAD command option. The only valid option is “ADD.”
Lab
The load labels.
Key
The coordinate system number defined by EDLCS or the element face number for the pressure loading.
Cname
The name of the existing component or part number to which this load will be applied.
Length
The number of data values for the time array
(Par1) and the load array
(Par2).
Phase
Phase of the analysis in which the load curve is to be used.
Par1
The time values, with the number of values in the string defined by
the Length argument (above).
Par2
The load values, with the number of values in the string defined by
the Length argument (above).
LCID
The curve ID, created using the EDCURVE command. If LCID is
nonzero, then Length= 1, and
Par1 and Par2
will be equal to 0.
Scale
The Scale Factor applied to the load curve.
Btime
The birth time.
Dtime
The death time.
This command also appears in the Command Reference. The format shown here contains information specific to the CDREAD/CDWRITE file.
The EDPREAD command is used to internally write the part information to the Jobname.CDB file for explicit dynamics. Prior to Release 8.0, the command format in Jobname.CDB is:
EDPREAD,R5.4,Nmat,Npart
Type, Mat, Real, UsedNmat
The number of materials.
Npart
Number of parts, and also, the number of times to repeat the second
Type,Mat,Real,Used
input line.
Type
The element type number.
Mat
The material number.
Real
The real constant set number.
Used
The flag indicating if the part is used (1), or not used (0).
For Release 8.0 and beyond, the command format is:
EDPREAD,R8.0,Nmat,Npart,Part ID
Type, Mat, Real, UsedNmat
The number of materials.
Npart
Number of parts, and also, the number of times to repeat the second
Type,Mat,Real,Used
input line.
PartID
The part number.
Type
The element type number.
Mat
The material number.
Real
The real constant set number.
Used
The flag indicating how many elements use
PartID. If USED = 0,
PartID is not used.
The EDWELD command is used to define a spotweld or a generalized weld for explicit dynamics.
There are two command formats (for spot and generalized welds). The command format for the spotweld appears in Jobname.CDB as follows:
EDWELD,R5.3,Option,NWELD,N1,N2,SN,SS,EXPN,EXPSOption
The EDWELD command option. The only valid option is “ADD.”
NWELD
The spotweld ID number.
N1
The node number of the first node connected by the spotweld.
N2
The node number of the second node connected by the spotweld.
SN
The normal force at the spotweld failure.
SS
The shear force at the spotweld failure.
EXPN
The exponent for spotweld normal force.
EXPS
The exponent for spotweld shear force.
The command format for the generalized weld appears in Jobname.CDB as follows:
EDWELD,R5.3,Option,NWELD,CNAME,,SN,SS,EXPN,EXPS,EPSF,TFAIL,NSW,CIDOption
The EDWELD command option. The only valid option is “ADD.”
NWELD
The generalized weld ID number.
CNAME
The name of the node component.
SN
The normal force at the weld failure.
SS
The shear force at the weld failure.
EXPN
The exponent for weld normal force.
EXPS
The exponent for weld shear force.
EXPF
The effective plastic strain at ductile failure.
TFAIL
The time of failure of the weld.
NSW
The number of spotwelds for the generalized weld.
CID
The coordinate system ID as defined by the EDLCS command.
This command also appears in the Command Reference. The format shown here contains information specific to the CDREAD/CDWRITE file.
The EN command is used to define an element . If an element contains more than eight nodes, the EN command is repeated until all nodes are defined. The command format in Jobname.CDB is:
EN,R5.5,Type,NUMN,I1,I2,I3,I4,I5,I6,I7,I8Type
The type of data to be defined. Valid labels are “ATTR” (read in element attributes), and “NODE” (read in nodes defining the element).
NUMN
The number of nodes.
I1,I2,I3,I4I5,I6,I7,I8The integer values to be read:
If Type is ATTR, the integer values
are the element attributes. Attributes are in the order:
NUMN,MAT,TYPE,REAL,SECNUM,ESYS,NUMELEM,SOLID,DEATH,EXCLUDE
If Type is NODE, the integer values
are the node numbers.
The LOCAL command defines a local coordinate system. The command format in Jobname.CDB is:
LOCAL,R5.0,Type,NCSY,CSYTYP,VAL1,VAL2,VAL3Type
The type of data to be defined. Valid labels are LOC (read in system origin), ANG (read in rotation angles), and PRM (read in system parameters).
NCSY
The coordinate system reference number.
CSYTYP
The coordinate system type (0, 1, 2, or 3).
VAL1,VAL2,VAL3Values to be read:
If Type is LOC, values are the
system origin in global Cartesian coordinates.
If Type is ANG, values are the
rotation angles in degrees.
If Type is PRM, values are the
first and second parameters of the system.
The M command defines a master degree of freedom. The command format in Jobname.CDB is:
M,R5.0,NODE,DlabNODE
The node number
Dlab
The DOF label
The MPDATA command defines a material property data table. You repeat the command until all properties are defined. The command format in Jobname.CDB is:
MPDATA,R5.0,LENGTH,Lab,MAT,STLOC,VAL1,VAL2,VAL3LENGTH
The total number of temperatures in the table.
Lab
The material property label. See the MP command description in Command Reference for valid labels.
MAT
The material reference number.
STLOC
The starting location in the table for the next three property values.
VAL1,VAL2,VAL3Property values assigned to three locations in the table starting at
STLOC.
The MPTEMP command defines a temperature table. You repeat the command until all temperature values are defined. The command format in Jobname.CDB is:
MPTEMP,R5.0,LENGTH,STLOC,TEMP1,TEMP2,TEMP3LENGTH
The total number of temperatures in the table
STLOC
The starting location in the table for the next three temperature values
TEMP1,TEMP2,TEMP3Temperatures assigned to three locations in the table starting at
STLOC
If the UNBLOCKED option is used with the CDWRITE command, then the N command defines a node. This is also the method used for defining nodes in .CDB files before ANSYS 5.4. The command format in Jobname.CDB is:
N,R5.3,Type,NODE,SOLID,PARM,VAL1,VAL2,VAL3Type
The type of data to be defined. Valid labels are LOC (read in coordinates) and ANG (read in rotation angles).
NODE
The node number.
SOLID
The solid model reference key. Not present for
Type= ANG.
PARM
Line parameter value (0 if not on line). Not present for
Type= ANG.
VAL1,VAL2,VAL3Values to be read:
If Type is LOC, values
are the coordinates in the global Cartesian
system.
If Type is ANG, values
are the rotation angles in degrees.
The NBLOCK command defines a block of nodes. This is the recommended method for inputting nodes into the ANSYS data base. The command syntax is:
NBLOCK, NUMFIELD, Solkey, NDMAX, NDSEL Format
NUMFIELD
The number of fields in the blocked format.
Solkey
The solid model key. The node is part of a solid model if the keyword SOLID appears here.
NDMAX
The maximum node defined.
NDSEL
The number of nodes written.
Data descriptors defining the format.
The format of the node "block" is as follows:
Field 1 - Node number.
Field 2 - The solid model entity (if any) in which the node exists (if SOLID key).
Field 3 - The line location (if the node exists on a line and if SOLID key).
Field 4 - 6 - The nodal coordinates.
Field 7 - 9 - The rotation angles (if NUMFIELD
> 3).
Only the last nonzero coordinate/rotation is output; any trailing zero values are left blank.
The final line of the block is always an N command using a -1 for the node number.
The following example shows a typical NBLOCK formatted set of node information. Note that this example has no rotational data. It contains only the first six fields.
NBLOCK,6,SOLID, 849, 723
(3i9,6e21.13e3)
1 0 0 8.7423930292124E-001 7.1843141243360E-001 8.2435547360131E-001
3 0 0 9.2314873336026E-001 9.3459943382943E-001 4.8406643591666E-001
4 0 0 1.1410427242574E+000 7.6883495387624E-001 2.5867801436812E-001
.
.
.
847 0 0 6.2146469267794E-001 8.0122597436764E-001 8.1352232529497E-001
848 0 0 8.1179373384170E-001 6.6711479947438E-001 7.6547291135454E-001
849 0 0 7.4952223718564E-001 7.6089019544242E-001 7.4112247735703E-001
N,R5.3,LOC, -1,If you are in the GUI, the NBLOCK command must be contained in an externally prepared file and read into ANSYS (i.e., CDREAD, /INPUT, etc.).
The NBLOCK command is not valid in a *DO loop.
*PREAD,Par,NUMVALS Format END PREAD
Par
Alphanumeric name to identify this parameter.
NUMVALS
Number of values.
Data descriptor defining the format of the subsequent lines (as needed). The format is always (4g20.13).
The R command defines a real constant set. You repeat the command until all real constants for this set are defined. The command format in Jobname.CDB is:
R,R5.0,NSET,Type,STLOC,VAL1,VAL2,VAL3NSET
The real constant set reference number.
Type
The type of data to be defined. LOC is the valid label.
STLOC
The starting location in the table for the next three constants.
VAL1,VAL2,
VAL3Real constant values assigned to three locations in the table starting
at STLOC.
The RLBLOCK command defines a real constant set. The real constant sets follow each set, starting with Format1 and followed by one or more Format2's, as needed. The command format is:
RLBLOCK,NUMSETS,MAXSET,MAXITEMS,NPERLINE
Format1
Format2NUMSETS
The number of real constant sets defined
MAXSET
Maximum real constant set number
MAXITEMS
Maximum number of reals in any one set
NPERLINE
Number of reals defined on a line
Data descriptor defining the format of the first line. For the RLBLOCK command, this is always (2i8,6g16.9). The first i8 is the set number, the second i8 is the number of values in this set, followed by up to 6 real constant values.
Data descriptors defining the format of the subsequent lines (as needed); this is always (7g16.9).
The real constant sets follow, with each set starting with Format1, and followed by one or more Format2's as needed.
The RLBLOCK command is not valid in a *DO loop.
The SE command defines a superelement. The command format in Jobname.CDB is:
SE,R5.5,File,,,TOLER,TYPE,ELEMFile
The name (case-sensitive) of the file containing the original
superelement matrix created by the generation pass
(Sename.SUB).
TOLER
Tolerance for determining whether use-pass nodes are noncoincident with master nodes having the same node numbers. Default = 0.0001.
TYPE
Element type number.
ELEM
Element number.
This command command also appears in the Command Reference. The format shown here contains information specific to the CDREAD/CDWRITE file.
The SECBLOCK command retrieves all mesh data for a user-defined beam section as a block of data. You repeat the command for each beam section that you want to read. The command format is:
SECBLOCK Format1 Format2 Format3
The First Line section. The first value is the number of nodes, and the second is the number of cells.
The Cells Section. The first 9 values are the cell connectivity nodes. The 10th (last) value is the material ID (MAT).
The Nodes Section. This section contains as many lines as there are nodes. In this example, there are 27 nodes, so a total of 27 lines would appear in this section. Each node line contains the node's boundary flag, the Y coordinate of the node, and the Z coordinate of the node. Currently, all node boundary flags appear as 0s in a cell mesh file. Because all node boundary flags are 0, SECBLOCK ignores them when it reads a cell mesh file.
Sample User Section Cell Mesh File
Following is a sample excerpt from a custom section mesh file for a section with 27 nodes, 4 cells, and 9 nodes per cell:
| First Line: |
27 4 |
| Cells Section: |
1 3 11 9 2 6 10 4 5 2
7 9 23 21 8 16 22 14 15 1
9 11 25 23 10 18 24 16 17 1
11 13 27 25 12 20 26 18 19 1
|
| Nodes Section: |
... 0 0.0 0.0 0 0.025 0.0 0 0.05 0.0 0 5.0175 0.0 0 19.98 10.00 0 20.00 10.00 ... |
The SECBLOCK command also retrieves data for shell sections. The command format is:
SECBLOCK,NTKn,MATn,THETAn,NUMPTn
N
Total number of layers. The second line
(TKn, MATn,
THETAn,
NUMPTn) is repeated
N times (once for each layer).
TKn
Layer thickness for layer number n
MATn
Material ID for layer number n (defaults to
element material ID)
THETAn
Layer orientation angle for layer number
n
NUMPTn
Number of integration points in layer number
n
The SECBLOCK command is not valid in a *DO loop.
The SFBEAM command defines a surface load on selected beam elements. Remaining values associated with this specification are on a new input line with a 4(1pg16.9) format. The command format in Jobname.CDB is:
SFBEAM,ELEM,LKEY,Lab,R5.0,DIOFFST,DJOFFST
ELEM
The element number.
LKEY
The load key associated with these surface loads.
Lab
A label indicating the type of surface load. PRES (for pressure) is the only valid label.
DIOFFST
Offset distance from node I.
DJOFFST
Offset distance from node J.
The SFE command defines a surface load. Values associated with this specification are on a new input line with a 4(1pg16.9) format. The command format in Jobname.CDB is:
SFE,ELEM,LKEY,Lab,KEY,R5.0ELEM
The element number.
LKEY
The load key associated with this surface load.
Lab
A label indicating the type of surface load: Valid labels are:
PRES (pressure)
CONV (convection)
HFLU (heat flux)
IMPD (impedance)
SEL (substructure load vector)
SELV (S. E. load vectors)
CHRG (charge density)
KEY
A value key. If it is 1, the values are real (film coefficient if convection). If it is 2, values are imaginary (bulk temperature if convection).