DAKOTA template keywords:

#name name to be displayed in template box

#docu
documentation to be displayed as tooltip
use html formatting and do not forget #!docu
#!docu


attribute definition:

- be aware that docu has to be inside "" if it contains colons!

<key, type (unsigned/int/double/bool/key/enum(val1; ...; valn)) [, default value, attribute name, docu, category, weight(int), always show(bool)]>

- designvariables:
number of design variables:
[dv_count]

initial values of design variables:
[dv_initial_values]

lower bounds of design variables:
[dv_lower_bounds]

upper bounds of design variables:
[dv_upper_bounds]

names of design variables:
[dv_names]


It is important to keep the following order of keywords inside your template definition:
1. objectives
2. evaluations
3. inequality constraints
4. equality constraints

- evaluations:
total number of objectives + evaluations:
[eval_count_all]

number of objectives:
[eval_count_objective]

number of evaluations
[eval_count_evaluation]

names of objectives + evaluations
[eval_names_all]

names of objectives
[eval_names_objective]

names of evaluations
[eval_names_evaluation]

- constraints:
total number of inequality + equality constraints:
[constr_count_all]

total number of equality constraints:
[constr_count_equality]

total number of inequality constraints:
[constr_count_inequality]

names of inequality + equality constraints:
[constr_names_all]

names of equality constraints:
[constr_names_equality]

names of inequality constraints:
[constr_names_inequality]


response surface creation:
-> checks for string 'model.dat' in template file and writes yellow bin to be used as sample points by dakota
example:
<reuse_samples all points_file = 'model.dat', key, true, Use Result Pool, Use Result Pool for Response Surface Generation, response surface creation, 0, true>