Bulk Data Entry
MPCADD – Multipoint Constraint Set Combination
Description
Defines a multipoint constraint set as a union of multipoint constraint sets defined via MPC entries.
Format
(1) |
(2) |
(3) |
(4) |
(5) |
(6) |
(7) |
(8) |
(9) |
(10) |
MPCADD |
SID |
S1 |
S2 |
S3 |
S4 |
S5 |
S6 |
S7 |
|
|
S8 |
S9 |
etc. |
|
|
|
|
|
|
|
Field |
Contents |
SID |
Set identification number. (Integer > 0) |
Sj |
Set identification numbers of multipoint constraint sets defined via MPC entries. The Sj field should not reference the identification number of a multipoint constraint set defined by another MPCADD entry. (Integer > 0 or <PartName.number>) See comment 4. |
1. | Multipoint constraint sets must be selected with the Subcase Information command MPC=SID. |
2. | MPCADD entries take precedence over MPC entries. If both have the same SID, only the MPCADD entry will be 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 MPCADD 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: