1Blurb:: 2Run analysis drivers that are linked-to or compiled-with %Dakota 3 4Description:: 5Direct interfaces are used to compile/link simulation programs into 6%Dakota and to invoke Dakota's built-in algebraic test problems. 7 8Direct simulation interfaces communicate variable and response data 9in-core instead of through the filesystem. This typically requires 10modification to simulator programs so that they can be linked into 11%Dakota; however it can be more efficient due to elimination of 12external processes and auxilliary simulator output, more accurate due 13to higher numerics, and more flexible in terms of MPI parallelism. 14 15Direct interfaces are also used to invoke internal test functions that 16perform parameter to response mappings for simple functions as 17inexpensively as possible. These problems are compiled directly into 18the %Dakota executable as part of the direct function interface class 19and are used for algorithm testing. 20 21%Dakota supports direct interfaces to a few select simulation codes 22such as Matlab, Python, and Scilab. Another example is ModelCenter, a 23commercial simulation management framework from Phoenix 24Integration. To utilize this interface, a user must first define the 25simulation specifics within a ModelCenter session and then save these 26definitions to a ModelCenter configuration file. The \c 27analysis_components specification provides the means to communicate 28this configuration file to %Dakota's ModelCenter interface. 29 30Topics:: 31Examples:: 32The rosenbrock function is available as an executable, which can be 33launched with \ref interface-analysis_drivers-fork, and is also 34compiled with Dakota. The internal version can be used with: 35 36\verbatim 37interface 38 analysis_drivers = 'rosenbrock' 39 direct 40\endverbatim 41 42Theory:: 43Faq:: 44See_Also:: 45