# SET

Bulk Data Entry Defines a set of grids, elements, design variables, MBD entities, mode numbers, frequencies or times for reference by other input definitions.

## Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
SET SID TYPE SUBTYPE/

OPERATOR

ID1/

MODE1/

REAL1/

NAME1/

SID1/

X1/

G1/

ALL

ID2/

MODE2/

REAL2/

NAME2/p/

Y1

ID3/

MODE3/

REAL3/

NAME3/

SID3/

Z1

ID4/

MODE4/

REAL4/

NAME4/

SID4/

X2/

G2

ID5/

MODE5/

REAL5/

NAME5/

SID5/

Y2

ID6/

MODE6/

REAL6/

NAME6/

SID6/

Z2

ID7/

MODE7/

REAL7/

NAME7/

SID7

ID8/

MODE8/

REAL8/

NAME8/

SID8

ID9/

MODE9/

REAL9/

NAME9/

SID9

etc. etc. etc. etc. etc. etc. etc.
etc. etc.

## Alternate Format for ID Ranges

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
SET SID TYPE SUBTYPE
ID1 THRU ID2 EXCEPT ID3 ID4 ID5 ID6
ID7 etc. ENDTHRU
etc.

## Example 1

The following set contains the grids 1, 17, 22, 23, 29, 33, 35, 48, 88, 93 and 102. It is defined using a simple ID list (assuming that these GRID cards are present in the Bulk Data).
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
SET 56 GRID LIST
88 93 17 1 23 29 35 48
33 102 22

## Example 2

The following set contains the elements 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 33, 34, 34, 35, 36, 37, 38, 41, 42, 43, 44, 45, 94, 95, 96. 97, 98, 99, 106, 107, 108, 109, 110, 111, 120, 121 and 125. It is defined using a combination of ID ranges and lists.
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
SET 56 ELEM LIST
11 THRU 22
33 THRU 45 EXCEPT 39 40
94 THRU 111 EXCEPT 100 101 102 103
104 105 ENDTHRU
120 121 125

## Example 3

The following set includes any element included in sets 29, 30 or 31. It is defined as Boolean set.
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
SET 50 ELEM OR
29 30 31

## Example 4

The following set defines GRID/Component list; intended for use by PFMODE.
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
SET 11 GRIDC
12 T1 15 R2 128 T3

## Example 5

The following set defines list of strings.
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
SET 11 LABEL
LABEL1 LABEL2 TOP UPPER LOWER LEFT

## Example 6

The following set defines list of all elements with specific properties.
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
SET 11 ELEM PROP EXCEPT PHSELL
1 12 15 thru 128 555

## Example 7

The following set outputs all of the grids on PLOTEL.
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
SET ID GRID ELTYPE
PLOTEL

## Definitions

Field Contents SI Unit Example
SID Unique set identification. 1
Integer
Specifies an identification number for the set.
<String>
Specifies a user-defined string label for the set. 2

No default (Integer > 0 or <String>)

TYPE Identifies what type of entities the set is comprised of. 3
GRID
ELEM
RIGID
GRIDC
DESVAR
MODE
FREQ
TIME
LABEL
PLY

No default

SUBTYPE Indicates how the set is defined. 3
LIST (Default)
BBOX
PROP
MAT
ELTYPE
ELEM
DMIG

OPERATOR Operators supported in defining Boolean sets. 5 6 7
OR
AND
NOT
MINUS

No default

ID# ID list. Only valid for certain combinations of TYPE and SUBTYPE. The entity to which the ID corresponds depends on the TYPE and SUBTYPE of the set. 3

ID ranges may be used in combination with ID lists. The keywords EXCEPT and THRU are used to define ID ranges. The keyword ENDTHRU identifies the end of an ID range and is required if an ID list is to follow where the first value is within the previous range.

ID lists following EXCEPT must be in ascending order and must exist within the previous range.

No default (Integer > 0)

MODE# Mode number list. Only valid when TYPE is MODE. 3

Mode number ranges may be used in combination with Mode number lists. The same rules apply as for ID ranges.

No default (Integer ≥ 0) 11

REAL# Real value list. Only valid when TYPE is FREQ or TIME. 3

No default (Real)

NAME# Keyword list. Only valid for certain combinations of TYPE and SUBTYPE.

The keyword EXCEPT is allowed only as the first entry in a keyword list.

Default = Undefined 3

SID# Identification number of another SET definition. Used in defining Boolean sets. Only valid when OPERATOR is defined in SUBTYPE/OPERATOR field 5 6 7 8

No default (Integer > 0 or <PartName.number>)

X1, Y1, Z1, X2, Y2, Z2 X, Y, and Z coordinates of two opposing corners of a cuboid. Only valid when SUBTYPE is BBOX 3

No default (Real)

G1, G2 Grid ID's (G1, G2) can be used instead of (X1, Y1, Z1), (X2, Y2, Z2) data (see field descriptions above). G1, G2 should be defined in the basic coordinate system (CP field on the GRID entries should be blank).
ALL Keyword used for ID lists to indicate that all IDs of the appropriate entity type are to be included in the set.

Only valid in first field of ID list.

May be followed by keyword EXCEPT (see below).

THRU Keyword used for ID ranges to indicate that all IDs between the preceding ID and the following ID are to be included in the set.

Definition of range may contain list of exceptions in the following form:

N1 THRU N2 EXCEPT N3 N4 ... ENDTHRU

where, N1 ≤ N3 < N4... ≤ N2; N1 < N2

EXCEPT Keyword used for ID ranges and keyword lists to indicate that the following IDs or keywords are to be excluded from the set.

Only valid in first field for keyword lists.

When ALL is given as the first entry for an ID list, EXCEPT may be given as the second entry, in which case all subsequent IDs are excluded from the set of ALL entities of the defined TYPE.

ENDTHRU Optional keyword used after EXCEPT to indicate the end of an excluded ID list definition.

1. SID must be unique with respect to all other SET definitions (regardless of type). It must also be unique with respect to any SURF entries and any legacy SET/PSET I/O Options definitions.
2. String based labels allow for easier visual identification of sets, including when being referenced by other cards. (For example, the GSETID field in SPC). For more details, refer to String Label Based Input File in the Bulk Data Input File.
3. The following table describes subtype combinations and the set TYPE's for which they are valid.
TYPE SUBTYPE Description
GRID LIST or undefined This is a set of grids - structural grids (GRID) or scalar points (SPOINT) - defined either as a simple list of grid IDs, or as some combination of ranges of grid IDs and lists of grid IDs.
BBOX This is a set of grids defined by a bounding box. The fields X1, Y1, and Z1 provide the coordinates of one corner and X2, Y2, and Z2 the coordinates of an opposing corner of a cuboid. All grids contained within this cuboid are included in the set.

The bounding box can also be defined using the G1 and G2 fields instead of (X1, Y1, and Z1) and (X2, Y2, and Z2), respectively.

ELEM This is a set of structural grids (GRID) belonging to listed elements.
DMIG This is a set of grids belonging to the listed DMIG(‘s). DMIG's can either be listed by name (in the NAME# fields), or using the flag ALL (this would select grids of all DMIG’s).
ELEM LIST or undefined This is a set of elements defined either as a simple list of element IDs, or as some combination of ranges of element IDs and lists of element IDs.
BBOX This is a set of elements defined by a bounding box. The fields X1, Y1, and Z1 provide the coordinates of one corner and X2, Y2, and Z2 the coordinates of an opposing corner of a cuboid. All elements whose centroids are contained within this cuboid are included in the set.

The bounding box can also be defined using the G1 and G2 fields instead of (X1, Y1, and Z1) and (X2, Y2, and Z2), respectively.

PROP This is a set of elements defined in one of the following ways:
1. Through a list of property IDs, or some combination of ranges of property IDs and lists of property IDs. If multiple properties have the same ID (as PBAR may), they are all considered. All elements referencing the selected properties are included in the set.
2. Through a list of property types. All elements referencing properties of the listed type (PBAR, PCOMP, PSHELL, and so on) are included in the set.
3. Through a list of excluded property types. All elements except those referencing properties of the listed type, following the keyword EXCEPT, are included in the set.
4. List of property types or list of excluded property types may be followed by some combination of ranges of property IDs and lists of property IDs. All elements referencing properties satisfying both requirements (type and ID) are included in (or accepted from) the set.
MAT This is a set of elements defined through a list of material IDs, or some combination of ranges of material IDs and lists of material IDs. All elements referencing properties, that in turn reference the selected materials, are included in the set.
ELTYPE This is a set of elements defined in one of the following ways:
1. Through a list of element types. All elements of the listed type (CQUAD4, CHEXA, CBEAM, and so on) are included in the set.
2. Through a list of excluded element types. All elements except those of the listed type, following the keyword EXCEPT, are included in the set.
In addition to all valid element types, the following element type groupings may be used:
SOLID
For CTETRA, CPYRA, CPENTA and CHEXA elements referencing structural property definitions.
FLAT
SHELL
For FLAT elements referencing properties with non-zero MID2.
MEMBRANE
For FLAT elements referencing properties with zero MID2.
BEAM
For CBAR and CBEAM elements.
ROD
For CONROD and CROD elements.
FLUID
For CTETRA, CPYRA, CPENTA and CHEXA elements referencing fluid property definitions.
For rigid elements (RROD, RBAR, RBE1, RBE2 and RBE3). See RIGID below.
DMIG This is a set of elements belonging to the listed DMIG(‘s). DMIG’s can either be listed by name (in the NAME# fields), or using the flag ALL (this would select elements of all DMIG’s).
RIGID LIST or undefined This is a set of rigid elements defined either as a simple list of rigid element IDs, or as a combination of ranges of rigid element IDs and lists of rigid element IDs.
GRIDC LIST or undefined This is a set of GRID/Component pairs.
DESVAR LIST or undefined This is a set of design variables defined either as a simple list of design variable IDs, or as some combination of ranges of design variable IDs and lists of design variable IDs.
MODE LIST or undefined This is a set of mode numbers defined as a simple list of mode numbers, or as some combination of ranges of mode numbers and lists of mode numbers.

This can also reference a list of RANDPS Bulk Data Entry IDs. Such a SET Bulk Data Entry can be referenced by the RANDOM Subcase Entry.

FREQ LIST or undefined This is a set of real values representing frequencies defined simply as a list of real values.
TIME LIST or undefined This is a set of real values representing times defined simply as a list of real values.
LABEL LIST or undefined List of arbitrary labels. Each label must start with a letter and contain only letters or digits.
PLY LIST or undefined This is a set of ply ID's defined in the PLY or PCOMPG Data Entries.
4. SET definitions using may refer to non-existing entities. This is allowed, but the actual SET will contain only grids or elements which are present in the structure.
5. The Boolean operators OR, AND, NOT and MINUS are recognized for SET combinations.
Operator
Description
OR
An entity is included in the SET, if it is included in a minimum of one of the constituent sets. OR is used to expand the SET by combining items from various SET's (for example, an entity is included in SET, if it is present in SET1, SET2, or SET3, or ...).
AND
An entity is included in the SET, if it is included in all of the listed sets. AND is used to restrict the SET to a typically smaller subset (for example, an entity is included in SET, if it is present in SET1, SET2, and SET3, and ...).
NOT
An entity is included in the SET, if it is not included in the listed set (for example, if an entity is not included in SET 1, then it is included in SET).
Note: Only one set should be listed for the NOT operator.
MINUS
An entity is included in the SET if it is included in the first set, but not in the second set.
Note: Only two sets may be listed for when this operator is used.
6. Boolean SET definitions can only be used when all listed sets are of the same TYPE.
7. Boolean SET definitions can reference other Boolean sets, but circular references must be avoided. Boolean SET can be defined only for GRID, ELEM, or RIGID set types.
8. Supported local entries in specific parts can be referenced by the use of "fully-qualified references" on SET entries in the model. A fully-qualified reference (PartName.number) is similar to the format of a numeric reference. PartName is the name of the part that contains the referenced local entry (part names are defined on the BEGIN Bulk Data Entry in the model). number is the identification number of a referenced local entry in the part PartName. See Parts and Instances in the User Guide for detailed information on the use of fully-qualified references.

The SET Bulk Data Entry can be used in the global part to reference SET's defined within different parts. These SET entries in the global part can contain fully qualified references to part-specific SET data only if logical operators (OPERATOR field) are used. For example:

The following SET entry exists in part A:
BEGIN, FEMODEL, A
SET, 29, ELEM, LIST
15 THRU 30
...END, FEMODEL, A
Referencing SET, 29 in the global part G:
BEGIN, FEMODEL, G
SET, 78, ELEM, OR
A.29
...
END, FEMODEL, G
9. ELIST is an alternative to SET and SURF, but ELIST is intended only to provide compatibility with Nastran decks. It is recommended to use SURF/SET, instead of ELIST. Additionally,
• The SURF and SET entries may not be combined with ELIST entries to define damp elements.
• ELIST entries are internally converted to SET entries. If ELIST is referenced on a minimum of one MFLUID entry, then all MFLUID entries in a model must reference ELIST entries. In such cases, if an MFLUID entry references a particular Set Identification Number (<SID>) to define WSURF1/WSURF2 fields without a corresponding ELIST,<SID> in the model, then OptiStruct will not search for a SET/SURF,<SID>.
10. K2GG, M2GG, K42GG, B2GG, K22GGSUB, M2GGSUB, and B2GGSUB can reference SET of labels. Only one set can be referenced on each of these entries, but multiple such entries are supported.
11. In cyclic symmetry analysis, SET with TYPE = MODE can be used to specify the solution harmonic indices by referencing the SET in the HARMONICS I/O Options Entry, or the segment indices by referencing the SET in the NOUTPUT I/O Options Entry, where each mode number corresponds to a harmonic or segment index. Mode number of 0 is meaningful only for HARMONICS in cyclic symmetry analysis.
12. This card is represented as a set in HyperMesh.