DRESP2

This response can be a functional combination of any set of responses resulting from the design analysis iteration. Responses defined in this manner can be used as design objectives or constraints. The DRESP2 card identifies the equation to use for the response relationship and the input values to evaluate the response function.

Format

Example 1

Example 2

Associated Cards

Definitions

Comments

1. DRESP2 entries are referenced from the subcase through one of DESOBJ, DESSUB, or DESGLB.
2. DRESP2 entries must have unique identification numbers with respect to DRESP1 and DRESP3 entries.
3. DRESP1L, DRESP2L define a response defined with a DRESP1 or DRESP2, respectively, and a SUBCASE. The SUBCASE number 0 should be used for global responses. Similarly, DFREQ1L defines a corresponding DRESP1 response along with the SUBCASE ID to extract the loading frequencies associated with the DRESP1 response being referenced.
4. Responses with the same region identifier are grouped together into the same region. If the region identifier is blank, then a separate region is formed for each DRESP2 definition. The RTYPE EQUA on the DSCREEN definition refers to DRESP2 responses. It is important to ensure that responses with the same region identifier reference similar equations. For further information, refer to Constraint Screening in the User Guide.
5. Any number of VARTYPE# continuation lines can be defined. The order in which the VARTYPE# continuation lines are listed on the DRESP2 card is not specified. The same VARTYPE# can be repeated any number of times, in any position, on the card. However, the order in which the VARTYPE# continuation lines are listed will affect the solution as the values are passed to the equation (or function) in the listed sequence.
6. The entries on the DRESP2 cards are assigned to the variable on the DEQATN card in the order that they occur. For example 2 above x1 is the displacement response defined by the DRESP1 card with ID=9 and x2 is the displacement response defined by the DRESP1 card with ID=2.
7. DRESPi and DRESPiL cards cannot be mixed on the same DRESP2 definition.
8. If DRESP1L, DRESP2L, DFREQ1L are used for a constrained DRESP2, DESGLB must be used to identify the DRESP2.
9. If DRESP1L, DRESP2L, DFREQ1L are used in a DRESP2 objective function, then the DESOBJ that references the DRESP2 must be defined before the first Subcase.
10. If the DRESP2 data is referenced by DESOBJ data, the DESOBJ data must be above the first SUBCASE if:
    • The DRESP2 contains DRESP1L, DRESP2L, DFREQ1L data
    • The DRESP2 contains no DRESP1, DRESP2, DRESP1L, DFREQ1L, or DRESP2L data
    • The DRESP2 contains DRESP1, DRESP2 global responses

    The DESOBJ data must be in the correct SUBCASE if the DRESP2 contains subcase dependent DRESP1 responses.

11. DRESP2 cannot reference itself directly or recursively, but multiple levels of referencing are allowed.
12. The DGRID and DGRIDB VARTYPE's can be used to select grid point locations as variables to be passed to the specified equation or function. The grid point locations are specified as a list of Grid point ID/Component pairs where every second value is a component. The Grid point ID's are unique grid point identification numbers (ID) and Components are the grid point locations X1, X2, and X3 fields on the GRID Bulk Data Entry.

    
    
    

    DGRIDB:

    The VARTYPE DGRIDB can be used to select grid point locations in the basic coordinate system. The basic coordinate system is the default rectangular coordinate system in OptiStruct.

    DGRID:

    The VARTYPE DGRID can be used to select the grid point locations in the local coordinate system of each grid point. This local coordinate system may be specified by the CP field of the GRID Bulk Data Entry for a particular grid point of interest. All local (or user-defined) coordinate systems are directly or indirectly based on the default basic coordinate system.

    The VARTYPE DGRIDL can be used to select grid point locations as variables to be passed to the specified equation or function with respect to a user-defined coordinate system. The grid point locations are specified as a list of Grid point ID, Components, and Coordinate system IDs, where every second value is a component and ever third value is a user-defined coordinate system ID. The Grid point ID's are unique grid point identification numbers (ID) and Components are the grid point locations X1, X2, and X3 fields on the GRID Bulk Data Entries.

    
    
    

    DGRIDL:

    The VARTYPE DGRIDL can be used to select the grid point locations in a user-defined coordinate system for each component. This user-defined coordinate system may be specified as every third value. All local (or user-defined) coordinate systems are directly or indirectly based on the default basic coordinate system.

13. The following functions can be used instead of an EQID. If FUNC is used, the DEQATN entry is no longer needed. The functions are applied to all arguments on the DRESP2 regardless of their type.

    Function	Description	Formula
    SUM	Sum of arguments	$\mathit{SUM}(y_1,y_2\dots y_m)=\sum _{j=1}^m{y}_j$
    AVG	Average of arguments	$\mathit{AVG}(y_1,y_2,\dots y_m)=\left[\sum _{j=1}^m{y}_j\right]/m$
    SSQ	Sum of square of arguments	$\mathit{SSQ}(y_1,y_2\dots y_m)=\sum _{j=1}^m{y}_j^2$
    RSS	Square root of sum of squares of arguments	$\mathit{RSS}(y_1,y_2\dots y_m)=\sqrt{\sum _{j=1}^m{y}_j^2}$
    MAX	Maximum of arguments
    MIN	Minimum of arguments
    SUMABS	Sum of absolute value of arguments	$\mathit{SUM}(y_1,y_2\dots y_m)=\sum _{j=1}^m\left|y_j\right|$
    AVGABS	Average of absolute value of arguments	$\mathit{AVG}(y_1,y_2\dots y_m)=\left[\sum _{j=1}^m\left|y_j\right|\right]/m$
    MAXABS	Maximum of absolute arguments
    MINABS	Minimum of absolute value of arguments
    RMS	Root mean square value of arguments	$\mathit{RMS}(y_1,y_2,\dots ,y_m)=\sqrt{\frac{1}{m}\left(\sum _{i=1}^m{y}_i^2\right)}$

14. Multiple RID-Model Name pairs can be specified on a single DRESPM continuation line. These responses can be used similar to responses defined via the VARTYPE# -ID# entries. ASSIGN, MMO can be used to identify the filename of the model and the user-defined Model Name that contains the referenced response definition.
15. An inconsistent number of responses can be referenced via multiple DRESP#L VARTYPE's. The following requirements should be met for such entries:
    • A minimum of one DRESP# entry listed on a corresponding DRESP#L VARTYPE should reference only a single response value, (and)
    • DRESP# entries listed on other DRESP#L VARTYPE's should reference the same number of responses.
    • If requirement (1) above is not met, then the number of responses referenced by all the DRESP# entries (listed on all the DRESP#L VARTYPE's) should be equal.
    Acceptable Example:

    DRESP1  1       R1      STRESS  ELEM       SVM3      1
    2                
    DRESP1  2       R2      STRESS  PSHELL     SVM4      1 
    DRESP2  3       MA          1   
    +       DRESP1L        4   0
    +       DRESP1L        2   2       
    DRESP1  4       vol       VOLUME
    DEQATN  1       f(a,b)=a+b     

    Not Acceptable Example:

    DRESP1  1       R1      STRESS  ELEM        SVM1      1  
     2                
    DRESP1  2       R2      STRESS  PSHELL      SVM2      1 
    DRESP2  3        MNA         1        
    +       DRESP1L        4   0 
    +       DRESP1L        1   2  
    +       DRESP1L        2   2  
    DRESP1  4       vol       VOLUME                                  
    DEQATN  1       f(a,b,c)=a+b+c                                             

    In the Acceptable example, the number of responses referenced by DRESP1L=4 is one. Also, DRESP1L=2 references multiple responses, this is acceptable as there are no other DRESP#L that reference more than one response. However, in the "Not Acceptable" example, DRESP1L=1 references two responses and DRESP1L=2 references multiple responses (this violates requirement 2 above).

16. The VTYPE#, RID#, and VOPT# fields can be used to identify the DRESP1 and DRESP2 responses to be passed as vectors to the DRESP2 entry. The VTYPEL#, RID#, LID#, and VOPT# fields can be used to identify the subcase-specific DRESP1 and DRESP2 responses to be passed as vectors to the DRESP2 entry.
17. The DFREQ1, DFREQ1L, DFREQ1V, and DFREQ1LV options are available to pass loading frequencies from a corresponding frequency-based DRESP1 response to the DRESP2/DRESP3. This is supported for Frequency Response and Random Response Optimization responses.

    DFREQ1

    Loading frequency corresponding to a frequency-based response.

    DFREQ1L

    Loading frequency corresponding to a frequency-based subcase-specific response. Subcase ID should also be provided.

    DFREQ1V

    Vector of loading frequencies for a particular frequency-based response (ATTB field of the corresponding DRESP1 can be blank to pass all loading frequencies of interest corresponding to the referenced DRESP1 response).

    DFREQ1LV

    Vector of loading frequencies for a particular frequency-based subcase-specific response. Subcase ID should also be provided. (ATTB field of the corresponding DRESP1 can be blank to pass all loading frequencies of interest corresponding to the referenced DRESP1 response).

18. This card is represented as optimization responses in HyperMesh.