Skip to content

Commit fa7c1d4

Browse files
committed
Add documentation for LOCALIZATION keyword
1 parent 84fabdf commit fa7c1d4

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
@@ -494,6 +494,62 @@ are correctly associated with reservoir zones.
494494
If a zone is specified but no ZONEMAP is provided, or if the observation location doesn't match
495495
the expected zone, the observation will be deactivated with a warning during the simulation.
496496

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

499555
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)