Bulk Data Entry
SPCADD – Single-Point Constraint Set Combination
Description
Defines a single-point constraint set as a union of single-point constraint sets defined via SPC or SPC1 entries.
Format
(1) |
(2) |
(3) |
(4) |
(5) |
(6) |
(7) |
(8) |
(9) |
(10) |
SPCADD |
SID |
S1 |
S2 |
S3 |
S4 |
S5 |
S6 |
S7 |
|
|
S8 |
S9 |
|
-etc- |
|
|
|
|
|
|
Field |
Contents |
SID |
New single-point constraint set identification number. (Integer > 0) |
Si |
Single-point constraint sets identification numbers defined via SPC or SPC1 entries. The Si values must be unique. (Integer > 0 or <PartName.number>) See comment 4. |
1. | The Si field should not reference the identification number of a single-point constraint set defined by another SPCADD entry. |
2. | SPCADD entries take precedence over SPC or SPC1 entries. If both have the same set ID, only the SPCADD entry is used. |
3. | If all Si are non-existent, the solver will exit with an error termination. |
4. | Supported local entries in specific parts can be referenced by the use of “fully qualified references” on SPCADD 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’s Guide for detailed information on the use of fully qualified references. |
5. | This card is represented as a loadcollector in HyperMesh. |
See Also: