Dakota Reference Manual: system

| Dakota Reference Manual Version 6.15 Explore and Predict with Confidence

- Main Page
- Related Pages

All Pages
system

(Not recommended) Launch analysis drivers with a system call

## Specification

Alias: none

Argument(s): none

Child Keywords:

| Required/Optional | Description of Group | Dakota Keyword | Dakota Keyword Description
--- | --- | --- | --- | ---
| Optional | parameters_file | Specify the name of the parameters file
| Optional | results_file | Specify the name of the results file
| Optional | file_tag | Tag each parameters & results file name with the function evaluation number
| Optional | file_save | Keep the parameters & results files after the analysis driver completes
| Optional | labeled | Requires correct function value labels in results file
| Optional | aprepro | Write parameters files in APREPRO syntax
| Optional | work_directory | Perform each function evaluation in a separate working directory
| Optional | allow_existing_results | Change how Dakota deals with existing results files
| Optional | verbatim | Specify the command Dakota uses to launch analysis driver(s) and filters

## Description

The system call interface is included in Dakota for portability and backward compatibility. Users are strongly encouraged to use the `fork` interface if possible, reverting to system only when necessary. To enable the system call interface, replace the `fork` keyword with `system`. All other keywords have identical meanings to those for the fork interface

## See Also

These keywords may also be of interest:

- fork