Download and Install Dakota
Download Dakota
Command Line Only
7.0.0 macOS | Windows | Linux (RHEL8) | Linux (RHEL9) | Source (zip) | Source (tar.gz)
6.24.0 macOS | Windows | Linux (RHEL8) | Source (zip) | Source (tar.gz)
6.23.0 macOS | Windows | Linux (RHEL8) | Source (zip) | Source (tar.gz)
6.22.0 macOS | Windows | Linux (RHEL8) | Source (zip) | Source (tar.gz)
6.21.0 macOS | Windows | Linux (RHEL8) | Source (zip) | Source (tar.gz)
6.20.0 macOS | Windows | Linux (RHEL8) | Source (zip) | Source (tar.gz)
6.19.0 macOS | Windows | Linux (RHEL7) | Linux (RHEL8) | Source (zip) | Source (tar.gz)
6.18.0 macOS | Windows | Linux (RHEL7) | Linux (RHEL8) | Source (zip) | Source (tar.gz)
6.17.0 macOS | Windows | Linux (RHEL7) | Linux (RHEL8) | Source (zip) | Source (tar.gz)
6.16.0 macOS | Windows | Linux (RHEL7) | Source (zip) | Source (tar.gz)
Command Line + GUI
6.23.0 macOS | Windows | Linux (RHEL8)
6.22.0 macOS | Windows | Linux (RHEL8)
6.21.0 macOS | Windows | Linux (RHEL8)
6.20.0 macOS | Windows | Linux (RHEL8)
6.19.0 macOS | Windows | Linux (RHEL7) | Linux (RHEL8)
6.18.0 macOS | Windows | Linux (RHEL7) | Linux (RHEL8)
6.17.0 macOS | Windows | Linux (RHEL7) | Linux (RHEL8)
6.16.0 macOS | Windows | Linux (RHEL7)
GUI Only
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
If you wish, rename the extracted Dakota binary executable directory to something more convenient:
$ ls
dakota-release.platform
$ mv dakota-release.platform Dakota
Because Dakota executables are not signed, their attributes must be cleared before they will work on macOS. To do so, run the following command, substituting the path of your Dakota install for “Dakota”:
$ xattr -cr 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, highlight 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.
Python Environment
Dakota’s pre-built binaries include several compiled Python extension modules:
dakota.environment— Run Dakota studies using an input filedakota.study— Full Python APIdakota.surrogates— Python interface to the surrogates moduledakota.ext_method— external Python method support
The above RHEL8, RHEL9, and macOS downloads for release 7.0 are compiled against Python 3.13 and will only load in a Python 3.13 interpreter. (Our Windows binaries currently are not distributed with full Python support.) If your system Python is a different version, you will need to create a dedicated Python 3.13 environment. Miniconda is a convenient way to do this on any platform:
# Download and install Miniconda, then:
conda create -n dakota python=3.13
conda activate dakota
With the environment active, install any additional packages you need.
To use dakota.study, Pydantic >= 2.12 is required:
pip install "pydantic>=2.12"
Then set PYTHONPATH to include Dakota’s Python directory as described in
Setting Your Environment, or use the
install-python target if you built from source.
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.
Alternative: register the Python package automatically (Linux/Mac)
If you built Dakota from source and want import dakota to work without
setting PYTHONPATH by hand, run the install-python build target after
a normal install:
make install-python
This writes a dakota.pth file into the site-packages directory of the
Python interpreter Dakota was configured with (the active venv or conda env if
one is active, otherwise your user site-packages). The package files stay in
$INSTALL_DIR/share/dakota/Python, so existing RPATHs are preserved.
To undo the registration run make uninstall-python.
Note: install-python targets the interpreter chosen at CMake configure
time (-DPython3_EXECUTABLE=...). If you later switch environments, re-run
make install-python from the new environment. Because Dakota’s Python
components are built for a specific major.minor version of Python (e.g. 3.14),
if the Python version in the new environment differs, a complete re-configure and
re-build will be needed, not just a fresh install.
Make Changes in Bash Shell
Edit your Bash startup file in your favorite text editor. For Linux, this is ~/.bashrc. macOS 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 macOS:
export PATH=$INSTALL_DIR/bin:$INSTALL_DIR/share/dakota/test:$INSTALL_DIR/gui/Dakota_UI_<version>.app/Contents/MacOS:$PATH
export PYTHONPATH=$PYTHONPATH:$INSTALL_DIR/share/dakota/Python
Replace Dakota_UI_<version>.app with the name of the GUI application in your
installation. To see it, run ls $INSTALL_DIR/gui.
Save and close file.
Update changes in your shell window.
$ source ~/.bashrc # Or other startup file on macOS
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 macOS:
set path=($INSTALL_DIR/bin $INSTALL_DIR/share/dakota/test $INSTALL_DIR/gui/Dakota_UI_<version>.app/Contents/MacOS $path)
setenv PYTHONPATH "${PYTHONPATH}:${INSTALL_DIR}/share/dakota/Python"
Replace Dakota_UI_<version>.app with the name of the GUI application in your
installation. To see it, run ls $INSTALL_DIR/gui.
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?

