ConfigurationΒΆ
ERT requires some set-up. For example:
Distributions must be assigned to priors.
The forward model must be described so that ERT can run it.
Observations must be provided.
The analysis algorithms you want to use must be parameterized.
If running on an HPC cluster, you will have to tell ERT how to interact with the queue system.
There are prescribed ways to provide all of this information, and ERT has strict formatting requirements for its configuration file. However, it also provides convenient syntax and structure for dealing with almost any scenario.
This chapter sets out everything you need to know to configure ERT.
- The ert configuration file format
- Data types
- Forward model
- Observations
- List of keywords
- Commonly used keywords
- NUM_REALIZATIONS
- DEFINE
- DATA_FILE
- DESIGN_MATRIX
- ECLBASE
- JOBNAME
- GRID
- NUM_CPU
- REALIZATION_MEMORY
- DATA_KW
- RANDOM_SEED
- ENSPATH
- HISTORY_SOURCE
- REFCASE
- INSTALL_JOB
- INCLUDE
- OBS_CONFIG
- PRIORITIZE_PRIVATE_IP_ADDRESS
- RUNPATH
- RUNPATH_FILE
- RUN_TEMPLATE
- Keywords controlling the simulations
- MIN_REALIZATIONS
- SUBMIT_SLEEP
- STOP_LONG_RUNNING
- MAX_RUNNING
- MAX_RUNTIME
- Parameterization keywords
- Analysis module
- Keywords controlling the ES algorithm
- Advanced keywords
- Keywords related to running the forward model
- Workflow hooks
- Queue system
- Magic strings