.. _interface-analysis_drivers-fork-results_format-json_format: """"""""""" json_format """"""""""" Expect results files in JSON format **Specification** - *Alias:* None - *Arguments:* None - *JSON argument key:* None - *Default:* true **Description** When this keyword is used, Dakota expects results files written by an analysis driver or output filter to be in JSON format, which is explained :ref:`here `. Some strengths of the JSON format are that it is a widely used format for data interchange, and the metadata it includes reduce the potential for driver bugs. **Examples** .. tab:: Freeform .. code-block:: dakota interface fork analysis_drivers 'driver.py' parameters_file = "params.in" results_file = "results.out" results_format json .. tab:: JSON .. code-block:: json { "interface": [ { "analysis_drivers": {"drivers": ["driver.py"]}, "interface_type": {"fork": {}}, "parameters_file": "params.in", "results_file": "results.out", "results_format": {"json_format": {}} } ] }