These console scripts are called as Dakota’s analysis_driver: dakota_run_component for a CSDMS component, and dakota_run_plugin for a model interfaced by a Dakotathon plugin class.
Defines the dakota_run_component console script.
dakotathon.run_component.
main
()[source]¶Handle arguments to the dakota_run_component console script.
dakotathon.run_component.
run_component
(params_file, results_file)[source]¶Brokers communication between Dakota and a CSDMS component.
This console script provides a generic analysis driver for a Dakota experiment. At each evaluation step, Dakota calls this script with two arguments, the names of the parameters and results files:
Once the component is identified, a worker is created to perform three steps: preprocessing, execution, and postprocessing. In the preprocessing step, information from the configuration file is transferred to the component. In the execution step, the component is called, using the information passed from Dakota. In the postprocessing step, output from the component is read, and a single statistic (e.g., mean, median, max, etc.) is applied to it. This number, one for each response, is returned to Dakota through the results file, ending the Dakota evaluation step.
Defines the dakota_run_plugin console script.
dakotathon.run_plugin.
run_plugin
(params_file, results_file)[source]¶Brokers communication between Dakota and a model through files.
This console script provides a generic analysis driver for a Dakota experiment. At each evaluation step, Dakota calls this script with two arguments, the names of the parameters and results files:
Once the model is identified, an interface is created to perform three steps: preprocessing, execution, and postprocessing. In the preprocessing step, information from the configuration file is transferred to the component. In the execution step, the component is called, using the information passed from Dakota. In the postprocessing step, output from the component is read, and a single statistic (e.g., mean, median, max, etc.) is applied to it. This number, one for each response, is returned to Dakota through the results file, ending the Dakota evaluation step.