DDVAL

Bulk Data Entry Define real, discrete design variable values for discrete variable optimization or to define relative rotor spin rates in rotor dynamics.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
DDVAL ID DVAL1 DVAL2 DVAL3 DVAL4 DVAL5 DVAL6 DVAL7  

Alternate Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
DDVAL ID DVAL1 "THRU" DVAL "BY" INC      

The continuation entry formats (shown below) may be used more than once, and in any order. They may also be used with either format above.

Continuation Entry Format 1

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
  DVAL8 DVAL9 DVAL10 DVAL11 etc.        

Continuation Entry Format 2

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
  DVAL8 "THRU" DVAL9 "BY" INC        

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
DDVAL 110 0.1 0.2 0.3 0.5 0.6 0.4    
  .7 thru 1.0 by 0.05        
  1.5 20              

Definitions

Field Contents SI Unit Example
ID Unique discrete value set identification number.

(Integer > 0)

 
DVALi Discrete values. The DVALi sequence can be random.

(Real or "THRU" or "BY")

 
INC Discrete value increment.

(Real)

 

Comments

  1. DDVAL entries must be referenced by:
    • the DDVAL field of a DESVAR
    • the SPTID field of a RSPINR Bulk Data Entry
  2. If the bounds on DESVAR cards (either XLB and/or XUB) are wider than those given by the discrete list of values on the corresponding DDVAL entry, XLB and/or XUB on DESVAR will be replaced by the minimum and maximum discrete values.
  3. Trailing fields on a DDVAL record can be left blank if the next record is of type DVALi "THRU" DVALj "BY" INC. Also, fields 7 through 9 must be blank when the type DVALi "THRU" DVALj "BY" INC is used in fields 2 through 6. Fields 8 through 9 must be blank when the type DVALi "THRU" DVALj "BY" INC is used in fields 3 through 7 for the first record. Embedded blanks are not permitted in other cases.
  4. The format DVALi "THRU" DVALj "BY" INC defines a list of discrete values, for example, DVALi, DVALi+INC, DVALi+2.0*INC, …, DVALj. The last discrete DVALj is always included, even if the range is not evenly divisible by INC.
  5. This card is represented as a discrete design variable in HyperMesh.