Simple Example

First Steps

  1. Make sure Dakota runs.
    You should see Dakota version information when you type:
    dakota -v
  2. Create a working directory for your Dakota files.
  3. Copy rosen_multidim.in from the $DAKOTA_INSTALL/examples/users directory to the working directory, where $DAKOTA_INSTALL is the Dakota installation directory.
  4. From the working directory, run:
    dakota -i rosen_multidim.in -o rosen_multidim.out rosen_multidim.stdout

What should happen

Dakota outputs a large amount of information to help users track progress. Four files should have been created:

  1. The screen output has been redirected to the file rosen_multidim.stdout. The contents are messages from Dakota and notes about the progress of the iterator (i.e. method/algorithm).
  2. The output file rosen_multidim.out contains information about the function evaluations.
  3. The file rosen_multidim.dat is created due to the specification of tabular graphics data and tabular graphics file. This summarizes the variables and responses for each function evaluation.
  4. The file dakota.rst is a restart file. If a Dakota analysis is interrupted, it can be often be restarted without losing all progress.

In addition to the files, some plots are created due to the specification of graphics. These can be helpful when processing the data or diagnosing unexpected results. Dakota has some data processing capabilities built in. The output file will contain the relevant results. In this case, the output file has details about each of the 81 function evaluations. For more advanced or customized data processing or visualization, the tabular data file can be imported into another analysis tool.

What now?

  • Assuming Dakota ran successfully, skim the three text files (restart files are in a binary format). These are described further in the Dakota User's Manual, Section 2.1.3.
  • This example used a parameter study method, and the Rosenbrock test problem. More details about the example are in Dakota User's Manual, Section 2.3.2 and the test problem is described in Sections 2.3.1 and 21.2.
  • Explore the many methods available in Dakota in the Dakota User's Manual, Chapters 3 - 8.
  • Try running the other examples in the same directory. These are mentioned throughout the Dakota User's Manual and listed in Chapter 2, Table 2.1 for convenience.
  • Learn the syntax needed to use these methods. For running Dakota see the Section 2.4, and for input file information see Section 2.2.
  • Learn how to use your own analysis code with Dakota in Chapter 17.