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/latest/lib/python3.9/site-packages/ert/shared/hook_implementations/workflows/export_misfit_data.py

Other#

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/latest/lib/python3.9/site-packages/ert/shared/hook_implementations/workflows/export_runpath.py

DISABLE_PARAMETERS#

The DISABLE_PARAMETERS workflow disables parameters,

so they are excluded from the update step. The job takes a group of parameters as input:

DISABLE_PARAMETERS DISABLE_PRED

The parameters that are given as arguments will be removed from the update.

Note that unknown parameter names will be silently ignored.

This workflow is recommended to be run as a PRE_FIRST_UPDATE hook.

An example to disable parameters in three steps follows.

First, in the ert config file, include:

LOAD_WORKFLOW disable_parameter_pred HOOK_WORKFLOW disable_parameter_pred PRE_FIRST_UPDATE

GEN_KW DISABLE_PRED pred.tmpl pred.json pred_priors GEN_KW COEFFS coeff.tmpl coeffs.json coeff_priors

The content of “coeff_priors” could be for example:

COEFF_A UNIFORM 0 1 COEFF_B UNIFORM 0 2 COEFF_C UNIFORM 0 5

And the content of “pred_priors”:

COEFF_D UNIFORM 1 3 COEFF_E UNIFORM 5 9

Second, make a new file called “disable_parameter_pred” with:

DISABLE_PARAMETERS DISABLE_PRED

Finally, after running the ert config file, the user can check the plots (e.g. in the gui click “Create plots”) that the disabled parameters were not updated. For the example above, there would be two groups of parameters:

COEFFS:COEFF_A COEFFS:COEFF_B COEFFS:COEFF_C

DISABLE_PRED:COEFF_D DISABLE_PRED:COEFF_E

All the parameters in the COEFFS group are updated from one iteration to the next, e.g. the standard deviation or/and distribution of the parameters are updated. At the same time, the parameters in the DISABLE_PRED group are not updated and they have the same distribution and sampling in all iterations and realizations.

Category
other
Source package
ert
Job configuration used by ERT#
INTERNAL      True
SCRIPT        /home/docs/checkouts/readthedocs.org/user_builds/ert/envs/latest/lib/python3.9/site-packages/ert/shared/hook_implementations/workflows/disable_parameters.py