Main Input Keywords

Setting (setting)

log_level_cmd

Set the level of logging messages printed to the command line.

• Optional

• Type: String

• Arguments: debug|info|warning|error|critical

• Default: info

Use the default Python logging levels (case insensitive). debug prints the most information, while critical prints the least.

log_level_file

Set the level of logging messages printed to the log file.

• Optional

• Type: String

• Arguments: debug|info|warning|error|critical

• Default: info

Use the default Python logging levels (case insensitive). debug prints the most information, while critical prints the least.

log_file_name

Set the name of the log file.

• Optional

• Type: String

• Arguments: Any valid file name

• Default: log.txt

Listing 21 Example

setting:
  log_level_cmd: "info"
  log_level_file: "debug"
  log_file_name: "eval.log"
  data_process_functions_file: "data_proc_funcs"

Structure (structure)

name

Name of the structure. Used only in logging messages.

• Optional

• Type: String

• Arguments: Arbitrary

• Default: structure_0

parameter

Key-value pairs of the design parameters for the whole structure.

• Optional

• Type: Dictionary

• Arguments: key: value pairs

• Default: None

Listing 22 Example

structure:
  parameter:
    param1: "value1"
    param2: 2
    param3: 3.0
    param4: 4e5
    param5: true  # or on
    param6: false  # or off

design

Basic design setup of the structure.

• Optional

• Type: Dictionary

Listing 23 Example

structure:
  name: "uh60_blade_1"
  parameter:
    cs_template: 'airfoil_gbox_uni.xml.tmp'
    airfoil: 'SC1095.dat'
    a2p1: 0.8
    a2p3: 0.6
    airfoil_point_order: -1
    lam_skin: "T300 15k/976_0.0053"
    lam_cap: "Aluminum 8009_0.01"
    lam_spar: "T300 15k/976_0.0053"
    lam_front: "T300 15k/976_0.0053"
    lam_back: "T300 15k/976_0.0053"
    ssc_spar: "[-45/0/45/90]"
  design:
    type: 'discrete'
    dim: 1
    cs_assignment:
      all: 'main_cs'
  cs:
    main_cs:
      base: 'cs'
      model: 'md1'

Cross-section library (cs)

This block contains a list of cross-sectional base designs.

Listing 24 Example

cs:
  - name: "cs_base_design_1"
    ...
  - name: "cs_base_design_2"
    ...

name

Name of the cross-sectional base design.

• Required

• Type: String

• Arguments: Arbitrary

• Default: None

parameter

Key-value pairs of the design parameters for the current CS.

• Optional

• Type: Dictionary

• Arguments: key: value pairs

• Default: None

design

Basic design setup of the current CS.

• Optional

• Type: Dictionary

tool

PreVABS command used to create the cross-section.

• Optional

• Type: String

• Default: prevabs

base_file

File name of the cross-sectional design template.

• Required

• Type: String

• Default: None

Listing 25 Example

cs:
- name: "cs"
  parameter:
    cs_template: 'airfoil_gbox_uni.xml.tmp'
    mdb_name: "material_database_us_ft"
    rnsm: 0.001
    gms: 0.004
    mat_nsm: "lead"
    mat_fill_front: "Rohacell 70"
    mat_fill_back: "Plascore PN2-3/16OX3.0"
    mat_fill_te: "Plascore PN2-3/16OX3.0"
  design:
    dim: 2
    tool: 'prevabs_153_dev'
    base_file: cs_template
  model:
    md1:
      tool: 'vabs'

Analysis (analysis)

Listing 26 Example

analysis:
  steps:
    - step: "step 1"
      type: "cs"
      ...
    - step: "step 2"
      ...

steps

Specification of analysis steps.

• Required (at least one step)

• Type: List

• Default: None

step

Name of the current step.

• Required

• Type: String

type

Type of the current analysis step.

• Required

• Type: String

• Arguments: cs|script

cs defines a cross-sectional analysis step. script defines a custom step using user-provided Python scripts.

Related pages

• Custom script analysis step

analysis

Use under:

analysis:
  steps:
    - step: "..."
      type: "cs"
      analysis: "..."

Specify the cross-sectional analysis type.

• Required

• Type: String

• Arguments: h|fi

file

Use under:

analysis:
  steps:
    - step: "..."
      type: "script"
      file: "..."

Name of the custom Python script file.

• Required

• Type: String

Related pages

• Custom script analysis step

function

Use under:

analysis:
  steps:
    - step: "..."
      type: "script"
      function: "..."

Name of the custom Python function.

• Required

• Type: String

Related pages

• Custom script analysis step

args

Use under:

analysis:
  steps:
    - step: "..."
      type: "script"
      args:
        - arg1
        - arg2
        - ...

Extra positional arguments passed to the custom Python function.

• Optional

• Type: List

Related pages

• Custom script analysis step

kwargs

Use under:

analysis:
  steps:
    - step: "..."
      type: "script"
      kwargs:
        kw1: arg1
        kw2: arg2
        ...

Extra keyword arguments passed to the custom Python function.

• Optional

• Type: Dictionary

Related pages

• Custom script analysis step

Listing 27 Example

analysis:
  steps:
    - step: "cs analysis"
      type: 'cs'
      analysis: 'h'
    - step: "calc diff"
      type: "script"
      file: 'data_proc_funcs'
      function: "dakota_postpro"
      kwargs:
        beam_properties: ["gj", "ei22", "ei33"]
        target: [2.29e3, 3.98e3, 2.44e5]

Design study configuration (study)

Most of the keywords in this block are the same as those of Dakota. See their documentation for more information.

Related pages:

• Design Study

Listing 28 Example

study:
  method:
    format: "keyword"
    output: "normal"
    soga:
      max_function_evaluations: 10
      population_size: 5
      seed: 1027
      print_each_pop: true
  variables:
    data_form: "compact"
    data: |
      a2p1, design, continuous, 0.7:0.9
      a2p3, design, continuous, 0.5:0.7
  responses:
    data_form: "compact"
    data: |
      diff_gj,   objective, min, 0.5
      diff_eiyy, objective, min, 0.8
      diff_eizz, objective, min, 0.8
  interface:
    fork:
      parameters_file: "input.in"
      results_file: "output.out"
      file_save: on
      work_directory:
        directory_tag: on
        directory_save: on
    required_files:
      - "design/*"
      - "scripts/*"