DCONSTR
Bulk Data Entry Defines design constraint upper and lower bounds where response is defined by DRESP1, DRESP2, and DRESP3 cards.
Format
(1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) |
---|---|---|---|---|---|---|---|---|---|
DCONSTR | DCID | RID | LBOUND/ LTID |
UBOUND/ UTID |
LFREQ/ LOCBUCK |
UFREQ | PROB | RATIO |
Example
(1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) |
---|---|---|---|---|---|---|---|---|---|
DCONSTR | 1 | 9 | 0.5 | 10.0 |
Associated Cards
(1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) |
---|---|---|---|---|---|---|---|---|---|
DRESP1 | 9 | TOPN | DISP | 3 | 4668 |
Definitions
Field | Contents | SI Unit Example |
---|---|---|
DCID | Design constraint
identification number. (Integer > 0) |
|
RID | DRESP1,
DRESP2, or DRESP3
identification number. (Integer > 0) |
|
LBOUND/LTID | Lower bound on response or
table identification number of a TABLEDi entry
that specifies the lower bound as function of a loading frequency.
See Comments. (Real, Integer, or blank) |
|
UBOUND/UTID | Upper bound on response or
table identification number of a TABLEDi entry
that specifies the upper bound as function of a loading frequency.
See Comments. (Real, Integer, or blank) |
|
LFREQ/LOCBUCK |
|
|
UFREQ | Upper bound on a loading
frequency range. Default = 1.0E+20 (Real ≥ LFREQ) |
|
PROB | Probability value for
Reliability-based Design Optimization runs. (50.0 ≤ Real ≤ 100.0) |
|
RATIO | Flag indicating that the
constraint defined on the DCONSTR entry is the
constraint on the relative ratio of the response value at a
particular iteration and the corresponding value of the response at
iteration 0. 9 Default = Blank (RATIO or Blank) |
Comments
- The DCONSTR DCID is selected in the Subcase Information section by the DESSUB or DESGLB cards and/or referenced by the DCONADD card.
- For any DCID, the associated RID can be referenced only once.
- If LBOUND or UBOUND are blank, the corresponding constraint will not be generated for the bound (lower, upper, or both).
- Constraint bounds of zero should be avoided. Unnecessary bounds should be left blank. For example, lower bounds on von Mises stress should be blank, not zero. If a bound of zero is input, the bound will be changed to 1.0E-7 for lower bounds and -1.0E-7 for upper bounds. This will remove numerical difficulties and cause the constraints to be ignored unless the response is actually very near zero.
- LFREQ, UFREQ apply only to response types related to a frequency response subcase (DRESPi, RTYPE = FRDISP, FRVELO, FRACCL, FRSTRS, FRSTRN, FRFORC, and FRERP). The constraint bounds LBOUND and UBOUND are applied only if the loading frequency falls between LFREQ and UFREQ. If ATTB of DRESP1 specifies a frequency value, LFREQ and UFREQ are ignored.
- LTID, UTID identify a loading frequency dependent tabular input using TABLEDi. They are applied analogous to LFREQ, UFREQ. 5
- Equality constraints can be applied by setting LBOUND and UBOUND equal to the same value (which is the value of the constraint that the response is required to attain). The LBOUND/LTID and UBOUND/UTID fields should not reference Table ID's for equality constraints. Equality Constraints are only supported for Size, Shape Optimizations and the SQP or BIGOPT optimization algorithms should be used (see DOPTPRM,OPTMETH and Optimization Algorithms).
- The local buckling zone can be defined using DOPTPRM, BKLOCAL2 and DOPTPRM, BKLOCAL1. The LOCBUCK field can be used to specify the lower bound of the local buckling eigenvalue response. If the specified response is determined to be a local buckling mode, the LOCBUCK lower bound is utilized, otherwise, the LBOUND lower bound value is used for the response.
- The RATIO field is supported for all responses across DRESP1, DRESP2, and DRESP3. Optimization restart is supported and the updated constraint bounds are stored in the restart file. For iteration 0 in the .out file response summary, the original RATIO bounds are printed as the actual bounds are not known yet. The actual bounds are printed starting from iteration 1.
- This card is represented as an optimization constraint in HyperMesh.