Thank you for your interest in Dakota!

If you have never registered, please take a few minutes to  Register as a Dakota User. The information you provide is used to help us better understand our customers' needs. Please also subscribe to our mailing lists to participate in our public discussion forum and receive important Dakota announcements.

(Please note: registration is optional, and your information is solely used to improve user experience and provide usage statistics to our program sponsors.)

Downloads are provided for OS X, Windows, and Linux. The latest binaires were built on OS X 10.15, Windows 10, and Red Hat Enterprise Linux (RHEL) 7. The Linux binaries typically will not work on other Linux distributions, necessitating building from source. A notable exception is CentOS, which is binary compatible with RHEL. When compiling from source, Windows users should typically use a .zip Dakota source archive, while Mac, Linux, and other Unix-based OS users should typically use a Dakota .tar.gz source archive to avoid problems with source generation utilities and line ending conversion.

Packages for each supported OS that include the Dakota graphical UI are available. For convenience, command line interface (CLI)-only and GUI-only packages are also provided. The GUI-only packages are intended for users who have built the CLI version of Dakota from source and would also like to use the GUI, as we do not support building the GUI from source at this time.

Although we recommend using the most recent versioned release, we also provide "hot off the press" stable releases.

2/28/2022: Dakota's GUI uses the Log4j library for logging. A serious vulnerability in Log4j was announced in December 2021. To address the vulnerability, we have removed all downloads that contain affected versions of this library. We updated the GUI for Dakota versions 6.13, 6.14, and 6.15 with a more recent version of Log4j that is not affected by the vulnerability. Files that have a patch number (6.13.1, 6.14.1, and 6.15.1) in their names include the updated GUI. Executables in these files will still report the unpatched version number.