Workflow jobs¶

These are the workflow jobs installed in your ERT environment. To use them in the configuration file they must be included in a workflow and loaded in the configuration file as shown in Configure Workflows

Observations¶

Correlation¶

EXPORT_MISFIT_DATA¶

Will export misfit per observation and realization to a hdf file. The hdf file has the observation as key, and the misfit as values. The filename is “misfit.hdf” by default, but can be overridden by giving the filename as the first parameter: EXPORT_MISFIT_DATA path/to/output.hdf The misfit its calculated as follows: ((response_value - observation_data) / observation_std)**2

Category: observations.correlation
Source package: ert

Job configuration used by ERT¶

INTERNAL      True
SCRIPT        /home/docs/checkouts/readthedocs.org/user_builds/ert/envs/13.0.5/lib/python3.12/site-packages/ert/plugins/hook_implementations/workflows/export_misfit_data.py

MISFIT_PREPROCESSOR¶

MISFIT_PREPROCESSOR is removed, use ANALYSIS_SET_VAR OBSERVATIONS AUTO_SCALE”: example: ANALYSIS_SET_VAR OBSERVATIONS AUTO_SCALE * – all observations”

Category: observations.correlation
Source package: ert

Job configuration used by ERT¶

INTERNAL      True
SCRIPT        /home/docs/checkouts/readthedocs.org/user_builds/ert/envs/13.0.5/lib/python3.12/site-packages/ert/plugins/hook_implementations/workflows/misfit_preprocessor.py

Other¶

EXPORT_RUNPATH¶

The EXPORT_RUNPATH workflow job writes the runpath file.

The job can have no arguments, or one can set a range of realizations and a range of iterations as arguments. Note: no check is made for whether the corresponding runpath has been created.

Example usage of this job in a workflow:

EXPORT_RUNPATH

With no arguments, entries for iterations 0 and all realizations are written to the runpath file. The job can also be given ranges of iterations and realizations to run:

EXPORT_RUNPATH 0-5 | *

“|” is used as a delimiter to separate realizations and iterations. “*” can be used to select all realizations or iterations. In the example above, entries for realizations 0-5 for all iterations are written to the runpath file.

Category: other
Source package: ert

Job configuration used by ERT¶

INTERNAL      True
SCRIPT        /home/docs/checkouts/readthedocs.org/user_builds/ert/envs/13.0.5/lib/python3.12/site-packages/ert/plugins/hook_implementations/workflows/export_runpath.py

DISABLE_PARAMETERS¶

The DISABLE_PARAMETERS workflow has been moved to ert parameters.: Add GEN_KW <name> … UPDATE:FALSE

Category: other
Source package: ert

Job configuration used by ERT¶

INTERNAL      True
SCRIPT        /home/docs/checkouts/readthedocs.org/user_builds/ert/envs/13.0.5/lib/python3.12/site-packages/ert/plugins/hook_implementations/workflows/disable_parameters.py

CSV_EXPORT¶

Export of summary, misfit, design matrix data and gen kw into a single CSV file.

The script expects a single argument:

output_file: this is the path to the file to output the CSV data to

Optional arguments:

ensemble_list: a JSON string representation of a dictionary where keys are
UUID strings and values are ensemble names. A single * can be used to export all ensembles

design_matrix: a path to a file containing the design matrix

The script also looks for default values for output path and design matrix path to present in the GUI. These can be specified with DATA_KW keyword in the config file:

DATA_KW <CSV_OUTPUT_PATH> {some path} DATA_KW <DESIGN_MATRIX_PATH> {some path}

Category: other
Source package: ert

Job configuration used by ERT¶

INTERNAL      True
SCRIPT        /home/docs/checkouts/readthedocs.org/user_builds/ert/envs/13.0.5/lib/python3.12/site-packages/ert/plugins/hook_implementations/workflows/csv_export.py

GEN_DATA_RFT¶

Export of GEN_DATA based rfts to a CSV file. The csv file will in

addition contain the depth as duplicated seperate row.

The script expects four arguments:

output_file: this is the path to the file to output the CSV data to

key: this is the ert GEN_DATA key used for this particular RFT.

report_step: This is the report step configured in the ert
configuration file for this RFT.

trajectory_file: This is the the file containing the

Optional arguments:

ensemble_data_as_json: a comma separated list of ensembles to export (no spaces allowed)
if no list is provided the current ensemble is exported

Category: other
Source package: ert

Job configuration used by ERT¶

INTERNAL      True
SCRIPT        /home/docs/checkouts/readthedocs.org/user_builds/ert/envs/13.0.5/lib/python3.12/site-packages/ert/plugins/hook_implementations/workflows/gen_data_rft_export.py