SET

Format

Alternate Format for ID Ranges

Example 1

Example 2

Example 3

Example 4

Example 5

Example 6

Example 7

Definitions

Comments

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: 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. 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. 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. 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: Through a list of element types. All elements of the listed type (CQUAD4, CHEXA, CBEAM, and so on) are included in the set. 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 For CQUAD4, CQUAD8, CTRIA3 and CTRIA6 elements. 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. This card is represented as a set in HyperMesh.