Skip to content

Commit b6f4bdd

Browse files
committed
Add documentation for LOCALIZATION keyword
1 parent a3a6b78 commit b6f4bdd

2 files changed

Lines changed: 58 additions & 0 deletions

File tree

docs/ert/reference/configuration/observations.rst

Lines changed: 56 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -489,6 +489,62 @@ are correctly associated with reservoir zones.
489489
If a zone is specified but no ZONEMAP is provided, or if the observation location doesn't match
490490
the expected zone, the observation will be deactivated with a warning during the simulation.
491491

492+
The LOCALIZATION keyword - Configuring observations with location
493+
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
494+
495+
A prerequisite for using :ref:`distance based localization <distance_based_localization>`
496+
is to provide metadata regarding location for the observations.
497+
498+
This can be configured for :ref:`summary observations <summary_observation>` and
499+
:ref:`breakthrough observations <breakthrough_observation>` by inserting a `LOCALIZATION`
500+
keyword into their declarations.
501+
502+
The `LOCALIZATION` object has two required fields: `NORTH` and `EAST`. Additionally,
503+
`RADIUS` can be configured here, but will be defaulted to 3000m if absent.
504+
505+
The `LOCALIZATION` object can be defined as follows:
506+
507+
.. code-block:: none
508+
509+
LOCALIZATION {
510+
EAST=70;
511+
NORTH=80;
512+
RADIUS=2500;
513+
};
514+
515+
And inserted into a summary observation like so:
516+
517+
.. code-block:: none
518+
519+
SUMMARY_OBSERVATION WOPR_OP1_141 {
520+
KEY = WOPR;
521+
VALUE = 1e6;
522+
ERROR = 3e4;
523+
DATE = 2012-02-13;
524+
LOCALIZATION {
525+
EAST = 70;
526+
NORTH = 80;
527+
RADIUS = 2500;
528+
};
529+
};
530+
531+
And similarily into a :ref:`breakthrough observation <breakthrough_observation>`
532+
533+
The RFT observations already contains the keywords `NORTH` and `EAST` in its´ regular
534+
configuration. These observations are therefore already correctly configured for distance
535+
based localization.
536+
537+
The radius for RFTs will be the default radius value of 3000m, but can be overwritten by
538+
providing a `LOCALIZATION` object containing just the `RADIUS` key, e.g.
539+
540+
.. code-block::
541+
542+
LOCALIZATION {
543+
RADIUS=2500;
544+
};
545+
546+
547+
492548
.. _bulk_configuration_of_summary_observations:
493549

494550
Bulk configuration of summary observations

docs/ert/theory/gentle_introduction_to_history_matching.rst

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -520,6 +520,8 @@ That said, adaptive localization has some practical benefits.
520520
It is relatively easy to understand, and it can be enabled with minimal configuration.
521521
In practice, the only tunable input is the correlation threshold.
522522

523+
.. _distance_based_localization:
524+
523525
Distance based localization
524526
~~~~~~~~~~~~~~~~~~~~~~~~~~~
525527

0 commit comments

Comments
 (0)