Tutorial Example Files: The Cantilever Beam Problem
To precisely follow the examples in this tutorial, please use the following two files provided with Dakota:
- examples\training\201508\exercises\interfacing\2\cantilever (a Python script-based simulation model that receives input and provides output)
- examples\training\201508\exercises\interfacing\2\cantilever.i (a sample input file).
Upon launching the Dakota GUI for the first time, you will notice that there are four main areas on the screen:
Users of Eclipse will find this layout to be somewhat familiar. The four main panes on the screen are as follows:
- Project Navigator Tree (left area) – a tree view used for browsing all the components of a Dakota project.
- Settings Editor (center area) – the main area of the screen, used for displaying the details and settings of a specific component of a Dakota project.
- Text Editor (top-right area) – used for viewing and editing Dakota input text files.
- Console (bottom-right area) – used for viewing console output as Dakota is running.
The Dakota GUI allows you to reorganize the layout of panes on the screen as you wish using the standard Eclipse controls for views and perspectives. See Eclipse’s documentation on this topic if you wish to learn more.
Locate Your Dakota Executable
If you haven’t done so already, you need to let the Dakota GUI know where to find your Dakota command-line executable. To do this, go to Window > Preferences > Dakota:
Set the path for “Dakota executable” to the command-line executable’s location on your system, then click OK.