Getting Started

Download Dakota

Installation

Installing for Linux or Mac

Extract archive file into suitable install location, e.g. $HOME. If you have root access, you may extract archive file in a shared directory, e.g. /usr/local.

$ cd /path/to/Dakota/install/directory
$ tar xzvf /path/to/Dakota-release.platform.tar.gz

Rename the extracted Dakota binary executable directory:

$ ls
dakota-release.platform
$ mv dakota-release.platform Dakota

Set up your platform environment to access the Dakota executable, libraries, and tests.

Installing for Windows

Extract archive file into suitable install location, e.g. C:Dakota using the Windows extract utility.

In Windows Explorer window, highight Dakota.<release>.<platform>.zip file.
Right click and select “Extract All”
Select a destination, e.g. C:Dakota, and click the Extract button. In the instructions below, %dest_dir% refers to this destination directory.

Rename the extracted Dakota executable directory folder:

Right click the dakota-<release>.<platform> file, and select ‘Rename’.
Rename file to ‘Dakota’. In the instructions below, %install_dir% refers to the path to this new directory, %dest_dir%Dakota.

Set up your platform environment to access the Dakota executable, libraries, and tests.

Build from Source Code (Advanced)

For custom installations, download and build Dakota from source code.

Setting Your Environment

Setting Your Environment for Linux or Mac

Check your PATH Setting

In the instructions below, $INSTALL_DIR refers to the path to the new install directory, /path/to/dakota/install/directory/Dakota.

Make sure Dakota executables (and optionally test files and current directory) are available on the PATH by typing ‘which dakota’ at command line prompt. If your PATH variable is set correctly, the path to the dakota binary should be displayed.

$ which dakota
/path/to/dakota/install/directory/bin/dakota

If your PATH variable is NOT set correctly, you will get a message like the following:

$ which dakota
/usr/bin/which: no dakota in (/usr/local/bin:/usr/local/sbin)

The following setup will make the dakota command and other helper programs available at the terminal. If you prefer you may refer to the dakota executable using its fully-qualified path. Note, however, that some examples will require modification to work properly if dakota and related helper programs are not on your PATH.

To persist the PATH to Dakota across terminals/sessions, make the following changes to the appropriate shell login script. If you prefer to just test in your current terminal, execute the commands directly in a terminal.

Make Changes in Bash Shell

Edit your Bash startup file in your favorite text editor. For Linux, this is ~/.bashrc. OS X terminal runs a login shell, and so the start up file may be ~/.bashrc, ~/.bash_profile, ~/.bash_login, or ~/.profile. See the manpage for Bash for more information about the differences between login and non-login shells.
Modify and export PATH and PYTHONPATH. Type the following lines, replacing $INSTALL_DIR with the absolute path to your installation directory, e.g. $HOME. You need not add the gui path if you are not using the Dakota GUI, or PYTHONPATH if you do not plan to use the dakota.interfacing Python module.

On Linux:

export PATH=$INSTALL_DIR/bin:$INSTALL_DIR/share/dakota/test:$INSTALL_DIR/gui:$PATH
export PYTHONPATH=$PYTHONPATH:$INSTALL_DIR/share/dakota/Python

On OS X:

export PATH=$INSTALL_DIR/bin:$INSTALL_DIR/share/dakota/test:$INSTALL_DIR/gui/Contents/MacOS:$PATH
export PYTHONPATH=$PYTHONPATH:$INSTALL_DIR/share/dakota/Python

Save and close file.
Update changes in your shell window.

$ source ~/.bashrc # Or other startup file on OS X

Make Changes in C Shell

Edit the startup file ~/.cshrc in your favorite text editor.
Modify and export PATH and PYTHONPATH. Type the following lines, replacing $INSTALL_DIR with the absolute path to your installation directory, e.g. $HOME. You need not add the gui path if you are not using the Dakota GUI, or PYTHONPATH if you do not plan to use the dakota.interfacing Python module.

On Linux:

set path=($INSTALL_DIR/bin $INSTALL_DIR/share/dakota/test $INSTALL_DIR/gui $path)
setenv PYTHONPATH "${PYTHONPATH}:${INSTALL_DIR}/share/dakota/Python"

On OS X:

set path=($INSTALL_DIR/bin $INSTALL_DIR/share/dakota/test $INSTALL_DIR/gui/Contents/MacOS $path)
setenv PYTHONPATH "${PYTHONPATH}:${INSTALL_DIR}/share/dakota/Python"

Save and close file.
Update changes in your shell window.

$ source ~/.cshrc

Setting Your Environment for Windows

You will likely want to set the path to the Dakota executable. The following setup will make the dakota.exe command and other helper programs available at the command prompt. If you prefer you may refer to the dakota.exe executable using its fullly-qualified path. Note, however, that some examples will require modification to work properly if dakota.exe and related helper programs are not on your path.

Click the Start button and type ‘cmd’ in the ‘Search program and files’ text box to open cmd.exe.
At the command prompt, type the following command, replacing %install_dir% with the path to your Dakota installation:

set path=%path%;%install_dir%\bin;%install_dir%\test;%install_dir%\lib

Optionally, to install the dakota Python package, also perform:

set PYTHONPATH=%PYTHONPATH%;%install_dir%\share\dakota\Python

These changes are active as long as the current terminal window is open. To make them persistent, edit the system environment variables in the Windows system settings. This operation differs slightly from version to version of Windows. Consult the documentation for the one you use.

Test Installation

Make sure Dakota runs. You should see Dakota version information when you type:

dakota -v

Now what?

Learn how to run a simple example in Dakota.