Dakota Reference Manual  Version 6.12
Explore and Predict with Confidence
 All Pages

Limit the number of analysis drivers within an evaluation that Dakota will schedule


This keyword is related to the topics:


Alias: none

Argument(s): INTEGER

Default: local: unlimited concurrency, hybrid: no concurrency


When asynchronous execution is enabled and each evaluation involves multiple analysis drivers, then the default behavior is to launch all drivers simultaneously. The analysis_concurrency keyword can be used to limit the number of concurrently run drivers.